Windows 10: Quick Assist hangs/won't load on Azure Active Directory AAD joined Win 10 machine

Lrogers_aria · Dec 18, 2021

Hi,Really hoping someone will have insight on how to solve this.I need to do a screen sharing session with MS support for MS Teams in this case and MS has turfed all other remote assistance options outside of Quick Assist like Logmein. Problem being that when I try to launch Quick Assist on my fully updated Win 10 machine all I get is the spinning circle. Never loads. I've uninstalled and reinstalled it. Run an SFC scan and repair. Tried it in clean boot mode. Turned services on and off.Finally, I tried disconnecting my machine from Azure AD and logging in with just an outlook.com local acco

:)

Brink · Dec 18, 2021

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 · Dec 18, 2021

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...

SarahKong · Dec 18, 2021

Joining a Windows 10 Pro machine to Azure AD without linking/registering an employees email address to that computer

When joining a machine to Azure AD it requires an active Azure AD account to do this which be default is all. So i would leave that setting and just have the users join their own machines to Azure.

So you don't need to use your own account at all.

"Users may join devices to Azure AD - This setting enables you to select the users who can join devices to Azure AD. The default is All."

https://docs.microsoft.com/en-us/azure/active-d...

Does that answer your question?

Windows 10: Quick Assist hangs/won't load on Azure Active Directory AAD joined Win 10 machine

Quick Assist hangs/won't load on Azure Active Directory AAD joined Win 10 machine

Quick Assist hangs/won't load on Azure Active Directory AAD joined Win 10 machine

Quick Assist hangs/won't load on Azure Active Directory AAD joined Win 10 machine

Quick Assist hangs/won't load on Azure Active Directory AAD joined Win 10 machine - Similar Threads - Quick Assist hangs