Azure AD user account

%3CLINGO-SUB%20id%3D%22lingo-sub-1616157%22%20slang%3D%22en-US%22%3EAzure%20AD%20user%20account%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1616157%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20problem%20logging%20into%20the%20VLSC%20portal%20since%20the%20time%20i%20set%20up%20AD%20Connect%20with%20Azure%20from%20our%20local%20AD.%20Namely%20the%20VLSC%20login%20is%20connected%20to%20builtin%20domain%20administrator%20(%3CA%20href%3D%22mailto%3Aadministrator%40contoso.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Eadministrator%40contoso.com%3C%2FA%3E).%20Now%2C%20this%20user%20has%20attribute%20%22isCriticalObject%22%20set%20to%20true%2C%20therefore%20it%20will%20not%20sync%20to%20o365.%20As%20o365%20does%20not%20have%20this%20account%2C%20i'm%20unable%20to%20login%20to%20VLSC.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20question%20is%2C%20since%20o365%20is%20not%20aware%2C%20that%20%3CA%20href%3D%22mailto%3Aadministrator%40contoso.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Eadministrator%40contoso.com%3C%2FA%3E%26nbsp%3Bexists%20on%20premiss%2C%20can%20i%20simply%20create%20a%20new%20%3CA%20href%3D%22mailto%3Aadministrator%40contoso.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Eadministrator%40contoso.com%3C%2FA%3E%26nbsp%3Bin%20o365%20without%20any%20impact%20on%20local%20AD%20infrastructure%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20regards%2C%3C%2FP%3E%3CP%3ETibor%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1616157%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn-Premises%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1617083%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20AD%20user%20account%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1617083%22%20slang%3D%22en-US%22%3E%3CP%3EHey%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F696361%22%20target%3D%22_blank%22%3E%40tibor2120%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%20you%20can%20create%20one%20directly%20in%20office%20365%2C%20it%20shouldn't%20have%20any%20impact%20on%20on-premises%20environment.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hello,

 

I have a problem logging into the VLSC portal since the time i set up AD Connect with Azure from our local AD. Namely the VLSC login is connected to builtin domain administrator (administrator@contoso.com). Now, this user has attribute "isCriticalObject" set to true, therefore it will not sync to o365. As o365 does not have this account, i'm unable to login to VLSC.

 

My question is, since o365 is not aware, that administrator@contoso.com exists on premiss, can i simply create a new administrator@contoso.com in o365 without any impact on local AD infrastructure?

 

Best regards,

Tibor

1 Reply

Hey @tibor2120 ,

 

Yes you can create one directly in office 365, it shouldn't have any impact on on-premises environment.

 

Thanks