Windows 10 Enterprise Azure AD加入了混合AD Pro / Cons？ [英] Windows 10 Enterprise Azure AD Joined vs Hybrid AD Pro/Cons?

问题描述

我记得读过一些Windows 10功能只有在设备是本机Azure连接（非混合AD）和其他设备时才有效功能或用例需要混合AD。 我找不到我读到的页面。

I remember reading that some Windows 10 features only work if the device is native Azure-Joined (not hybrid AD) and other features or use cases require hybrid AD.  I can't find the page where I read that.

在哪里可以看到哪些当前Windows 10功能需要混合连接以及哪些功能需要直接连接到Azure AD？

Where can I see of which current Windows 10 features require hybrid join and which features require direct join to Azure AD?

推荐答案

您可能找到的链接不是官方微软前提。

The link you might have found is not an official Microsoft premise.

两者（本机）Azure AD Join和Hybrid Azure AD Join在条件访问和移动设备管理（MDM）方面提供相同的优势。但是，某些功能正在获取（本机）Azure AD Join和Hybrid
Azure AD Join之间的功能奇偶校验。针对Hybrid Azure AD Join目前通常不可用的（本机）Azure AD Join的功能包括：

Both (native) Azure AD Join and Hybrid Azure AD Join offer the same benefits in terms of conditional access and mobile device management (MDM). However, some features are in the process of getting feature-parity between (native) Azure AD Join and Hybrid Azure AD Join. Features that come into mind for (native) Azure AD Join that are currently not generally available (GA) for Hybrid Azure AD Join, include:

• AutoPilot（混合） AutoPilot是当前的公共预览版）
• FIDO2身份验证（当前在本地Azure AD加入的私有预览中）

两个加入之间的另一个主要区别 - 模型是Azure AD Join允许最终用户成为设备上的本地管理员;它类似于BYOD模型。 这就是为什么许多组织更喜欢混合Azure AD Join，其中组织的
权限模型，端点管理模型（包括ConfigMgr和GPO）和设备生命周期模型完全适用。

One other main difference between the two join-models is that Azure AD Join allows the end-user to become local administrator on the device; it resembles the BYOD model.  This is why many organizations prefer hybrid Azure AD Join, where the organization's permissions model, endpoint management model (including ConfigMgr and GPOs) and device lifecycle model apply fully.

这篇关于Windows 10 Enterprise Azure AD加入了混合AD Pro / Cons？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！