How do I delete/remove a "DISABLED" Managed account?

[Greg Schuler]

I recently set up an Organization for my company's Atlassian access and I verified the domain we use - lets call it red.com.  So I can now see all the "Managed accounts" that end with @Red.com.  I immediately noticed there are a log of "Managed accounts" that are, in fact, no longer valid accounts (that is, they are email addresses that have been removed from our domain a long time ago).   I assume these are showing up because they were used in the past to create/edit various items within our Atlassian applications?

In any case, I would like to not only DISABLE these accounts.  I would like to delete them - so I no longer see them anymore.  Is there a way to do this?

***

Also, in addition to having this Organization set up and our domain (red.com) validated, we previously linked our Atlassian products to G Suite - and our G Suite domain is... red.com.

When you have G Suite integration *and* Organization/domain verification and Managed accounts, what are the rules?  What takes precedence?  Are there best practices?

Thank you.

[AgentSmith]

Good Afternoon! Your assumption is accurate, Greg. The managed accounts displayed represent all users that have/had an Atlassian Account in Cloud. The distinguishing factor looking in Managed accounts is the product column (i.e. No product access, Confluence, JIRA Core, etc). 

Addressing the primary question, managed accounts can only be disabled and not deleted as per:

https://confluence.atlassian.com/cloud/atlassian-account-for-users-873871199.html#Atlassianaccountforusers-Managedaccounts 

Atlassian is now GDPR compliant: 

https://www.atlassian.com/blog/announcements/atlassian-and-gdpr-our-commitment-to-data-privacy

https://confluence.atlassian.com/gdpr/atlassian-cloud-right-to-erasure-950826022.html 

In other words, a support ticket needs to be submitted as we have a process to remove accounts.

About G-Suite and Atlassian Access:

It's possible for a site-admin to integrate G-Suite even if a domain verified by G-Suite are already verified by an Atlassian organization, the behavior is the same as if some other organization verified the same domain, it will become SUPERSEDED on the first Atlassian org.
In cases like the above, if the Atlassian organization verifies the domain again, it will become SUPERSEDED again by G-Suite every 4 hours, because of the syncing cycle.

Generally this can be avoided when/if the G-Suite admin and Atlassian org admins are aware of each others presence. 

Finally, due to the G-Suite sync cycle being automated, G-Suite will always take precedence. 

Hoping this helps.

[Romer Ventura]

Bump