Home

From Azure AD Registered devices to Hybrid Azure AD joined

%3CLINGO-SUB%20id%3D%22lingo-sub-290775%22%20slang%3D%22en-US%22%3EFrom%20Azure%20AD%20Registered%20devices%20to%20Hybrid%20Azure%20AD%20joined%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-290775%22%20slang%3D%22en-US%22%3EVery%20aware%20of%20the%20two%20technologies%20and%20how%20they%20differ%2Fwork%20and%20how%20to%20set%20u%20it%20up.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20inherited%20an%20old%20environment%20and%20they%20have%20all%20their%20Windows%2010%20devices%20Azure%20AD%20registered%20(not%20syncing%20OU%20with%20computer%20nor%20SCP%20etc%20setup).%3CBR%20%2F%3E%3CBR%20%2F%3EI%20want%20to%20move%20to%20Hybrid%20Azure%20AD%20joined.%20I%20know%20the%20steps%20but%20I%20wonder%20what%20will%20happen%20to%20all%20the%20800%2B%20Windows%2010%20devices%20already%20registered%3F%3CBR%20%2F%3E%3CBR%20%2F%3EWill%20they%20magically%20be%20replaced%20with%20Hybrid%20Azure%20AD%20joined%20objects%20in%20Azure%20AD%3F%20Will%20I%20get%20duplicate%20items%3F%20Do%20I%20need%20to%20do%20something%20on%20the%20client%20side%20or%20will%20daregcmd%20%2Fstatus%20simply%20show%20YES%3F%3CBR%20%2F%3E%3CBR%20%2F%3EAnyone%20done%20such%20switch%3F%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-290775%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20AD%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-357838%22%20slang%3D%22en-US%22%3ERe%3A%20From%20Azure%20AD%20Registered%20devices%20to%20Hybrid%20Azure%20AD%20joined%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-357838%22%20slang%3D%22en-US%22%3ECorrect%2C%20it%20seems%20to%20work%20(we%20use%20Conditional%20Access%20to%20require%20%22Hybrid%20Azure%20AD%20joined%22%20to%20access%20some%20cloud%20apps).%20However%2C%20you%20see%20duplicate%20devices%20in%20Azure%20AD%20(one%20that%20is%20Azure%20AD%20registered%20from%20before%20and%20one%20that%20is%20Hybrid%20Azure%20AD%20joined)%20and%20both%20of%20them%20seems%20to%20be%20active%20(there's%20a%20column%20saying%20ACTIVITY%20and%20it's%20recent%20on%20both).%20The%20client%20itself%20also%20sees%20itself%20as%20still%20Azure%20AD%20registered%20in%20Settings%20%26gt%3B%20Accounts%20%26gt%3B%20Access%20work%20or%20school.%20We%20tried%20removing%20the%20Azure%20AD%20registered%20device%20in%20Azure%20AD%20but%20the%20client%20does%20not%20remove%20itself%20locally%20in%20Settings%20so%20it's%20left%20there.%20Not%20very%20beautiful%20but%20at%20least%20it%20works%20and%20we%20focus%20to%20deploy%201809%20so%20it%20all%20solves%20by%20itself.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-357653%22%20slang%3D%22en-US%22%3ERe%3A%20From%20Azure%20AD%20Registered%20devices%20to%20Hybrid%20Azure%20AD%20joined%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-357653%22%20slang%3D%22en-US%22%3EThanks!%20So%20in%20your%20testing%2C%20devices%20below%201809%20that%20were%20already%20registered%20in%20Azure%20AD%20are%20indeed%20successfully%20hybrid%20joining%3F%20Does%20that%20create%20a%20duplicate%20device%20in%20Azure%20AD%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-357622%22%20slang%3D%22en-US%22%3ERe%3A%20From%20Azure%20AD%20Registered%20devices%20to%20Hybrid%20Azure%20AD%20joined%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-357622%22%20slang%3D%22en-US%22%3E%3CP%3EFrom%201607%20it%20should%20work%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Ftroubleshoot-hybrid-join-windows-current%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Ftroubleshoot-hybrid-join-windows-current%3C%2FA%3E%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3E%3CSPAN%3Ea%20work%20or%20school%20account%20was%20added%20prior%20to%20the%20completion%20of%20the%20hybrid%20Azure%20AD%20join.%20In%20this%20case%2C%20the%20account%20is%20ignored%20when%20using%20the%20Anniversary%20Update%20version%20of%20Windows%2010%20(1607).%3C%2FSPAN%3E%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3EBut%20you%20will%20still%20see%20the%20Azure%20AD%20registered%20device%20in%20Azure%20AD.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%201809%2C%20it%20will%20even%20remove%20the%20Azure%20AD%20registered%20device%20from%20Azure%20AD%20and%20remove%20it%20in%20the%20Windows%2010%20Settings%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Fhybrid-azuread-join-plan%23review-things-you-should-know%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Fhybrid-azuread-join-plan%23review-things-you-should-know%3C%2FA%3E%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3EAny%20existing%20Azure%20AD%20registered%20state%20would%20be%20automatically%20removed%20after%20the%20device%20is%20Hybrid%20Azure%20AD%20joined.%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3EThis%20is%20what%20we've%20seen%20so%20far%20during%20our%20testing.%20Let%20us%20know%20how%20your%20testing%20goes.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-357602%22%20slang%3D%22en-US%22%3ERe%3A%20From%20Azure%20AD%20Registered%20devices%20to%20Hybrid%20Azure%20AD%20joined%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-357602%22%20slang%3D%22en-US%22%3EWe%20have%20a%20very%20similar%20situation%20in%20my%20environment.%20What%20did%20you%20end%20up%20with%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-290781%22%20slang%3D%22en-US%22%3ERe%3A%20From%20Azure%20AD%20Registered%20devices%20to%20Hybrid%20Azure%20AD%20joined%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-290781%22%20slang%3D%22en-US%22%3EThanks%20for%20your%20quick%20reply.%3CBR%20%2F%3E%3CBR%20%2F%3EThey%20are%20on-premises%20AD%20joined%20%2B%20Azure%20AD%20Registered.%20I%20want%20to%20move%20to%20still%20on-premises%20AD%20joined%20%2B%20Hybrid%20Azure%20AD%20joined.%3CBR%20%2F%3E%3CBR%20%2F%3EHow%20do%20you%20manually%20Hybrid%20Azure%20AD%20join%20a%20client%20without%20creating%20the%20SCP%20record%3F%20This%20seems%20to%20be%20the%20first%20step%20in%20the%20guide%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Fhybrid-azuread-join-manual-steps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Fhybrid-azuread-join-manual-steps%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EFor%20the%20record%2C%20we're%20running%20PSH%2BSSO.%3CBR%20%2F%3E%3CBR%20%2F%3EOtherwise%2C%20the%20GPO%20to%20make%20sure%20the%20devices%20not%20to%20register%20automatically%20is%20a%20good%20idea%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Fhybrid-azuread-join-control%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Fhybrid-azuread-join-control%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-290780%22%20slang%3D%22en-US%22%3ERe%3A%20From%20Azure%20AD%20Registered%20devices%20to%20Hybrid%20Azure%20AD%20joined%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-290780%22%20slang%3D%22en-US%22%3EThey%20aren%E2%80%99t%20domain%20joined%20today%2C%20right%3F%3CBR%20%2F%3EJust%20try%20doing%20one%20manually%20before%20you%20setup%20the%20SCP!%20You%20could%20also%20set%20GPO%20not%20to%20auto%20register%20on%20those%20you%20don%E2%80%99t%20want%20to%20do%20a%20test%20run%20on%2C%20if%20you%20want%20to%20setup%20the%20SCP%20beforehand!%3CBR%20%2F%3EI%20believe%20they%20will%20not%20duplicate!%20Not%20100%20%25%20sure%20though%3CBR%20%2F%3E%3CBR%20%2F%3EAdam%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-752152%22%20slang%3D%22en-US%22%3ERe%3A%20From%20Azure%20AD%20Registered%20devices%20to%20Hybrid%20Azure%20AD%20joined%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-752152%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F19218%22%20target%3D%22_blank%22%3E%40Jonas%20Back%3C%2FA%3E%26nbsp%3B%20Just%20wanted%20to%20say%20thank%20you%20for%20this%20clarification%20as%20I%20am%20about%20to%20do%20this%20for%20my%20environment%20to%20prepare%20for%20an%20upgrade%20from%20O365%20(with%20AD%20registered%20devices%20but%20not%20AAD%20Connect%20synced)%20to%20M365%20(with%20hybrid%20join%20and%20AAD%20Connect%20synced).%26nbsp%3B%20The%20documentation%20from%20Microsoft%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Fhybrid-azuread-join-plan%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3Esays%26nbsp%3B%3C%2FP%3E%3CPRE%3EIf%20your%20Windows%2010%20domain%20joined%20devices%20are%20already%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Factive-directory%2Fdevices%2Foverview%23getting-devices-in-azure-ad%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20AD%20registered%3C%2FA%3E%20to%20your%20tenant%2C%20we%20highly%20recommend%20removing%20that%20state%20before%20enabling%20Hybrid%20Azure%20AD%20join.%3C%2FPRE%3E%3CP%3Ewithout%20really%20explaining%20the%20result%20of%20not%20doing%20this.%26nbsp%3B%20If%20the%20only%20consequence%20of%20this%20is%20a%20doubling%20up%2C%20that's%20no%20problem%3B%20we'll%20just%20delete%20the%20redunant%20ones%20from%20AAD%20via%20the%20Azure%20Portal.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-806049%22%20slang%3D%22en-US%22%3ERe%3A%20From%20Azure%20AD%20Registered%20devices%20to%20Hybrid%20Azure%20AD%20joined%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-806049%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F74084%22%20target%3D%22_blank%22%3E%40Ruairidh%20Campbell%3C%2FA%3E%26nbsp%3BWe%20have%20seen%20strange%20behaviors%20when%20running%20a%20device%20both%20Azure%20AD%20registered%20%2B%20Hybrid%20Azure%20AD%20joined%20at%20the%20same%20time%20when%20it%20comes%20to%20Conditional%20Access.%20For%20example%20if%20we%20set%20a%20rule%20in%20Conditional%20Access%20NOT%20to%20force%20MFA%20for%20Hybrid%20Azure%20AD%20joined%20it%20will%20still%20sometimes%20ask%20for%20MFA%20if%20the%20device%20is%20both.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20I%20still%20recommend%20making%20sure%20you%20don't%20end%20up%20there.%20Only%20way%20we%20found%20effective%20(without%20manual%20work%20on%20every%20client)%20-%20make%20sure%20to%20update%20them%20to%201809%2B%20before%20starting.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-879696%22%20slang%3D%22en-US%22%3ERe%3A%20From%20Azure%20AD%20Registered%20devices%20to%20Hybrid%20Azure%20AD%20joined%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-879696%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20trying%20to%20work%20through%20this%20today.%20I've%20set%20a%20GPO%20to%20set%20the%20SCP%20as%20I'm%20attempting%20a%20controlled%20setup%20against%20one%20machine.%20However%2C%20when%20sync%20the%20OU%20with%20the%20computer%20and%20the%20GPO%20is%20applied%2C%20the%20machine%20doesn't%20appear%20to%20do%20anything%20and%20the%20state%20of%20the%20machine%20doesn't%20change%20from%20Azure%20AD%20Registered%20to%20Hybrid%20Azure%20AD%20Joined.%20Any%20ideas%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-880603%22%20slang%3D%22en-US%22%3ERe%3A%20From%20Azure%20AD%20Registered%20devices%20to%20Hybrid%20Azure%20AD%20joined%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-880603%22%20slang%3D%22en-US%22%3EHave%20you%20enables%20Hybrid%20Azure%20AD%20Join%20in%20Azure%20AD%20Connect%3F%3C%2FLINGO-BODY%3E
Frequent Contributor
Very aware of the two technologies and how they differ/work and how to set u it up.

I inherited an old environment and they have all their Windows 10 devices Azure AD registered (not syncing OU with computer nor SCP etc setup).

I want to move to Hybrid Azure AD joined. I know the steps but I wonder what will happen to all the 800+ Windows 10 devices already registered?

Will they magically be replaced with Hybrid Azure AD joined objects in Azure AD? Will I get duplicate items? Do I need to do something on the client side or will daregcmd /status simply show YES?

Anyone done such switch?
10 Replies
They aren’t domain joined today, right?
Just try doing one manually before you setup the SCP! You could also set GPO not to auto register on those you don’t want to do a test run on, if you want to setup the SCP beforehand!
I believe they will not duplicate! Not 100 % sure though

Adam
Thanks for your quick reply.

They are on-premises AD joined + Azure AD Registered. I want to move to still on-premises AD joined + Hybrid Azure AD joined.

How do you manually Hybrid Azure AD join a client without creating the SCP record? This seems to be the first step in the guide: https://docs.microsoft.com/en-us/azure/active-directory/devices/hybrid-azuread-join-manual-steps

For the record, we're running PSH+SSO.

Otherwise, the GPO to make sure the devices not to register automatically is a good idea: https://docs.microsoft.com/en-us/azure/active-directory/devices/hybrid-azuread-join-control
We have a very similar situation in my environment. What did you end up with?

From 1607 it should work: https://docs.microsoft.com/en-us/azure/active-directory/devices/troubleshoot-hybrid-join-windows-cur...

a work or school account was added prior to the completion of the hybrid Azure AD join. In this case, the account is ignored when using the Anniversary Update version of Windows 10 (1607).

But you will still see the Azure AD registered device in Azure AD.

 

From 1809, it will even remove the Azure AD registered device from Azure AD and remove it in the Windows 10 Settings: https://docs.microsoft.com/en-us/azure/active-directory/devices/hybrid-azuread-join-plan#review-thin...

Any existing Azure AD registered state would be automatically removed after the device is Hybrid Azure AD joined.

This is what we've seen so far during our testing. Let us know how your testing goes.

Thanks! So in your testing, devices below 1809 that were already registered in Azure AD are indeed successfully hybrid joining? Does that create a duplicate device in Azure AD?
Correct, it seems to work (we use Conditional Access to require "Hybrid Azure AD joined" to access some cloud apps). However, you see duplicate devices in Azure AD (one that is Azure AD registered from before and one that is Hybrid Azure AD joined) and both of them seems to be active (there's a column saying ACTIVITY and it's recent on both). The client itself also sees itself as still Azure AD registered in Settings > Accounts > Access work or school. We tried removing the Azure AD registered device in Azure AD but the client does not remove itself locally in Settings so it's left there. Not very beautiful but at least it works and we focus to deploy 1809 so it all solves by itself.

@Jonas Back  Just wanted to say thank you for this clarification as I am about to do this for my environment to prepare for an upgrade from O365 (with AD registered devices but not AAD Connect synced) to M365 (with hybrid join and AAD Connect synced).  The documentation from Microsoft here says 

If your Windows 10 domain joined devices are already Azure AD registered to your tenant, we highly recommend removing that state before enabling Hybrid Azure AD join.

without really explaining the result of not doing this.  If the only consequence of this is a doubling up, that's no problem; we'll just delete the redunant ones from AAD via the Azure Portal.

@Ruairidh Campbell We have seen strange behaviors when running a device both Azure AD registered + Hybrid Azure AD joined at the same time when it comes to Conditional Access. For example if we set a rule in Conditional Access NOT to force MFA for Hybrid Azure AD joined it will still sometimes ask for MFA if the device is both.

 

So I still recommend making sure you don't end up there. Only way we found effective (without manual work on every client) - make sure to update them to 1809+ before starting.

I'm trying to work through this today. I've set a GPO to set the SCP as I'm attempting a controlled setup against one machine. However, when sync the OU with the computer and the GPO is applied, the machine doesn't appear to do anything and the state of the machine doesn't change from Azure AD Registered to Hybrid Azure AD Joined. Any ideas?

Have you enables Hybrid Azure AD Join in Azure AD Connect?
Related Conversations
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
30 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
7 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
29 Replies