Differences

This shows you the differences between two versions of the page.

--- azure:az-500:manage_azure_active_directory_azure_ad_identities [2022/06/27 23:12] – [B2C] mmuze
+++ azure:az-500:manage_azure_active_directory_azure_ad_identities [2022/07/22 13:44] (current) – mmuze
@@ Line 23: / Line 23: @@
       * [[https://docs.microsoft.com/en-us/microsoft-365/community/all-about-groups]]
       * The group's files are in SharePoint, the real time collaboration is in Teams, the email discussions are in Exchange, but they're all secured and managed as a Microsoft 365 Group.
+      * used for collaboration
 ====== Managed Identity ======
@@ Line 47: / Line 48: @@
 ====== B2C ======
   * [[https://docs.microsoft.com/en-us/azure/active-directory-b2c/overview]]
 > Azure Active Directory B2C provides business-to-customer identity as a service. Your customers use their preferred social, enterprise, or local account identities to get single sign-on access to your applications and APIs.
 {{ :azure:az-500:b2c.png?800 |}}
 ====== Administrative Unit ======
-  * An [[https://docs.microsoft.com/en-us/azure/active-directory/roles/administrative-units|Administrative Unit (AU)]] is a mechanism for limiting the permissions of an Azure AD role to apply to a selected set of users and/or groups. It limits the scope of the role. When a group is selected the scope only applies to the group itself, not the users that are a member of the group.
+  * An [[https://docs.microsoft.com/en-us/azure/active-directory/roles/administrative-units|Administrative Unit (AU)]] is a mechanism for limiting the permissions of an Azure AD role to apply to a selected set of users and/or groups instead of an entire AAD directory. It limits the scope of the role. When a group is selected the scope only applies to the group itself, not the users that are a member of the group.
 >  An administrative unit is an Azure AD resource that can be a container for other Azure AD resources. An administrative unit can contain only users, groups, or devices.