Windows 10: Join this device to Azure Active Directory option missing from windows 10/11

Dineshkumar Ponnuvel · May 18, 2022

Join this device to Azure Active Directory option missing from windows 10/11. We have checked after several restart and different account login. But still the same result.

:)

Brink · May 18, 2022

Windows 10 and Azure Active Directory: Embracing the Cloud

When we talked about new Windows 10 manageability choices back in November, we announced new capabilities that will enable Windows 10 to leverage Azure Active Directory. Since these capabilities are now starting to appear in the Windows 10 preview builds, this is a great time to explore them in more detail.

When talking about Windows 10 and Azure Active Directory, it’s important to understand that there are a few different scenarios that organizations may use:

Users will be able to join their work Windows 10 devices directly to Azure Active Directory and sign into Windows using their Azure Active Directory account and password – while still having single sign-on access to Office 365 and to on-premises services that leverage Active Directory authentication. The devices can be automatically enrolled into a mobile device management (MDM) service at the same time.

Users will be able to add their work account to their personal (BYOD) Windows 10 devices, establishing a link between Windows and their work account managed in Azure Active Directory, which will provide single sign-on access to the organization’s services. The devices may also be automatically enrolled in mobile device management (MDM).

Traditional PC devices, joined to an existing Active Directory domain, will have single sign-on access to cloud-based services like Office 365, the Windows Store, or any other Azure Active Directory-aware application. Windows 10 understands that the Active Directory account is associated with a synchronized Azure Active Directory account. (Device management continues to be provided using Active Directory Group Policy and System Center Configuration Manager.)

These scenarios provide organizations a great deal of flexibility – choose the scenario that makes the most sense for each device.

Since most organizations already use Active Directory, the logical next step for exploring Windows 10’s Azure Active Directory support is to set up directory integration between Active Directory and Azure Active Directory. For those that prefer more hands-on learning, check out the on-demand content from Microsoft Ignite.

But we don’t want to stop there, we have much more information to share. Alex Simons, Director of Program Management for the Identity and Services Division, and his team will be posting a series of blogs talking about Windows 10 and Azure Active directory, starting with this initial blog post.
Click to expand...

Source: http://blogs.windows.com/business/20...ing-the-cloud/

Nancy Xiong - MSFT · May 18, 2022

Can't join Azure Active Directory

I think you have known how to join your device to Azure AD. In this case, I'd like to explain some things to you.

For the Alternate Actions, A workstation group PC (non-domain joined computer) can display it.

If you just want users can access the resources from devices that meet your standards for security and compliance. You can register your device to Azure AD via + Connect.

For the differences between joining and registering devices to Azure AD, you can refer to this.

Joining a Windows 10 PC to Azure AD means you must sign in to Windows
using your Azure AD credentials and is mainly intended to be used on
devices which are solely used for work or study purposes and often
owned by the employer or school.

Registering a Windows 10 PC on Azure AD means you will continue
signing in to Windows with your personal local or Microsoft account,
but in addition can access employer / school resources with single
sign-on Azure AD credentials. Registering instead of joining is mostly
intended to be used when employees / students are allowed to use their
own devices for work or studies like in BYOD (Bring Your Own Device)
companies and schools, or just to allow employees / students do work /
school stuff from home.
Click to expand...

Brink · May 18, 2022

Windows Autopilot for existing devices supports Hybrid Azure AD Join

First, a quick refresher on Windows Autopilot for existing devices: For customers looking for a path to migrate from Windows 7 (or 8.1) to Windows 10 using Windows Autopilot, the challenge was always that you had to register the existing machines with Windows Autopilot in advance, but doing so was impossible because you couldn't grab the hardware hash from a device running Windows 7.

So, we added the ability in Windows 10, version 1809 to use a JSON file containing the equivalent of the Windows Autopilot profile so that you didn't have to register the device in advance; you could then tell Microsoft Intune to harvest the hash from the device later and register the device after the fact.

This solution worked great and has been leveraged by a number of organizations to move from Windows 7 and Active Directory to Windows 10 and Azure Active Directory, using Microsoft Intune (often with Configuration Manager for co-management) to deploy and manage the device.

But some organizations weren't yet ready for Azure AD Join (even with the Administrative Templates support in Microsoft Intune, and full support for Kerberos authentication from an Azure AD-joined device to Active Directory-secured resources) and asked us to support this same process, but with Hybrid Azure AD Join.

With this month's Microsoft Intune updates, we can now support this. And no client changes are needed: this works with Windows 10, version 1809 and above. All you need to do is specify a JSON file that specifies to join Active Directory (via Hybrid Azure AD Join) instead of Azure Active Directory - the rest of the process (e.g. the Configuration Manager task sequence that deploys Windows 10 to the device) is unchanged.

Note that you will need to target a Domain Join profile (and any other device-targeted policies) to "All devices" since the device won't be known to Microsoft Intune in advance. (Don't worry, this Domain Join profile has no impact on already-deployed devices, as it's only used by Microsoft Intune to determine what domain and OU should be used when joining a device to Active Directory.) See the updated documentation for more details.
Click to expand...

Source: https://techcommunity.microsoft.com/...re/ba-p/730408

Tweet

— Twitter API (@User) View on Twiiter

Windows 10: Join this device to Azure Active Directory option missing from windows 10/11

Join this device to Azure Active Directory option missing from windows 10/11

Join this device to Azure Active Directory option missing from windows 10/11

Join this device to Azure Active Directory option missing from windows 10/11

Join this device to Azure Active Directory option missing from windows 10/11 - Similar Threads - Join device Azure

Unable to join client machine to domain. Active Directory environment created in Azure.

Unable to join client machine to domain. Active Directory environment created in Azure.

Join this device to Azure Active Directory option missing from windows 10/11

Steps to detach device from Azure Active Directory and Domain

Azure Active Directory

Adding windows 10 PC to azure active directory

WIndows 10 Activation Issue / Azure AD joined device

Bitlocker and Azure Active Directory

Windows 10 and Azure Active Directory: Embracing the Cloud