This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 40%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES0%3C/text%3E%3C/svg%3E)
We tried enabling federation between Azure and ABM portal to automatically use UPN as appleid for ADE process, but had to discontinue because there were too many conflicting accounts because of which the client asked us to not enable this at last step.
However now when user tries to create an apple id with client email (same domain we were trying to enable federation with) it does not allows and says not recognised, this was working earlier. Can someone pls assist how to make this work again for users.
@svjs-0437 I have noticed that you enabled federation between Azure and ABM portal. If you don't want it, it is suggested to contact Azure AD to get more help. I will add "azure-ad-authentication". Let's wait for the related support engineer involved in this issue. Thanks.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 78%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESG%3C/text%3E%3C/svg%3E)
Just checking in to see if the below answer helped.
I will share my experience, we finally removed federation: When ABM federation is in progress there is no way to stop it
This is the correct behavior when the Federation is in progress.
You have a possibility to check how many accounts conflict after enabling Federation. It means that users, who created a personal Apple account using a corporate (federated) domain, should change it to their personal or after 60 days, the user’s personal Apple ID is automatically renamed to a temporary username.
Link with more detailed information. https://support.apple.com/en-in/guide/apple-business-manager/axme685676ac/1/web/1
Note: You cannot disconnect from a federated domain if Apple Business Manager is in the process of enabling federation or resolving conflicts with other Apple IDs.
Disconnect federation from a domain https://support.apple.com/en-in/guide/apple-business-manager/axmd952e0762/1/web/1
Please let me know if answer was helpful for you :)
i was attempting this but i keep getting the below error at the last step, any way to resolve this or anyway to reach apple for support?
What was the reason of the error. If you tried to disconnect federation, you won't be able to do it while all conflict won't be resolved or before 60 days after enabling.
Hello @Aleksandr Kolesnikov ,
This is informative and new to me. So client doesnt want to continue with federation bcos there are more number of conflicting accounts in the infra than expected. and we observed that we are no longer able to create new appleid with corporate email whcih i assume is because of this attempted federation enablement. So thats where we are trying to disconnect the federation to kill what was started and we ending up with above error. could you advise me on how to fix this?
Thank you for the help :)
also just noticed, we tried this federation setup in the start of JUne, so its way past 60days now, and still get this error, when attempting to disconnect federation.
There are a few way to solve it:
1) Check that you have sent notifications to users. Without this action conflicts won't start solving.
""Those users receive a mail message and a notification telling them they must rename their personal Apple ID. If they have not renamed their personal Apple ID after 60 days, the user’s personal Apple ID is automatically renamed to a temporary username, and the original username is released and claimed by your organisation." - this should fix conflicts.
2) Contact Apple support to disable federation from their side.
Please mark the answer as helpful :) Let me know what you've desided.
step 1 cant be a solution as client dont want to enable federation anymore
step 2 we tried, but not getting a respond, could you direct me where i can chek or raise and issue for this?
Thank you :)
Did you resolve this? We have the same situation and after we contacted Apple support they told us that federation process must be completed and after that it can be disabled.
"You cannot disconnect from a federated domain if Apple Business Manager is in the process of enabling federation or resolving conflicts with other Apple IDs."
@Djordje Novakovic There is no way to stop the procces. Especially if Apple support declined to do it from their side.
There are several ways how to manage this connection:
or you can wait 60 days, all personal Apple accounts with corporate email (domain) will be changed to random apple email.
Hi again, yes, Apple support declined to stop the process. We resolved conflicts after 60 days, last week screenshot, Disconnect button is still not available:
And today:
I see that "Disconnect" button is now available. I assume that we can disconnect it(according to Apple's documentation) now without enabling federation?
I will share my experience, we removed federation.
When ABM federation is in progress there is no way to stop it.
Resolve email conflicts.
After 60 days - when conflicts are resolved you can complete ABM federation or just disconnect it(this was my case).
Call Apple support, and they can check from their side when changes are propagated.
Remove your domain from ABM.
All existing accounts(admin accounts) will be automatically transferred to "yourDomain.appleid.com" and you can log in to ABM with that account.
After that Add your domain again in ABM and verify it.
After verification your admin accounts will be able to log in again with "@yourDomain".
Apple IDs can be created with "@yourDomain" again.