A hybrid environment is in place where the local on-premises Active Directory is connected to Azure Active Directory. After syncing a user, the User Principal Name is changed to use a custom domain to allow login to Microsoft services. However, users are now reporting issues logging in with their usernames, and upon checking the accounts in the Azure portal, it appears that the User Principal Name has reverted back to the onmicrosoft.com domain.

What steps can be taken to resolve this issue?

A hybrid environment is in place where the local on-premises Active Directory is connected to Azure Active Directory. After syncing a user, the User Principal Name is changed to use a custom domain to allow login to Microsoft services. However, users are now reporting issues logging in with their usernames, and upon checking the accounts in the Azure portal, it appears that the User Principal Name has reverted back to the onmicrosoft.com domain.

What steps can be taken to resolve this issue?

A hybrid environment is in place where the local on-premises Active Directory is connected to Azure Active Directory. After syncing a user, the User Principal Name is changed to use a custom domain to allow login to Microsoft services. However, users are now reporting issues logging in with their usernames, and upon checking the accounts in the Azure portal, it appears that the User Principal Name has reverted back to the onmicrosoft.com domain.

What steps can be taken to resolve this issue?