Removing verified domain while retaining user provisioning

[Kevin Gérard]

Hello, 

In our current setup we have verified our domain, and added a user provisioning to it. 

The problem we're experiencing with this is that i load close to 500 accounts with the domain, but only 70 of these should be loaded for our current setup. 

It also affects our billing, because some of these users are added to a Trello board, and are now suddenly billed! 

The idea now is to remove the verified domain, but RETAIN the user provisioning. 

That way i don't have 500 accounts in my system, and only the 70 i need are added to the environment. 

will the user provisioning work correctly without the verified domain? 

[Ed Letifov _TechTime - New Zealand_]

Hello, @[deleted] 

No you shouldn't need to invite anyone by email. 

Have you actually configured User Provisioning in Atlassian Access?

Was "Atlassian Cloud" application installed in Azure AD and configured correctly?

For some hints see these answers I've provided to others previously:

• https://community.atlassian.com/t5/Atlassian-Access-questions/Integrate-Azure-AD-with-Atlassian-Cloud/qaq-p/1852575
• https://community.atlassian.com/t5/Jira-Service-Management/Azure-AD-login-and-incoming-email-not-matching-up/qaq-p/1821809
• https://community.atlassian.com/t5/Confluence-questions/What-is-the-difference-between-site-access-and-product-access/qaq-p/1306257

Also this might be of help:

• https://community.atlassian.com/t5/Atlassian-Account-questions/SAML-SSO-with-Azure-AD-does-not-work-when-using-quot-Continue/qaq-p/2085502#M2218

[Deleted user]

Thank you very much @Ed Letifov _TechTime - New Zealand_ , I will go through this steps and will update.