![]() No cmdlets are exposed for creating or removing OUs however, so customers that are used to organize their processes around grouping users in OUs need to find a different solution. Thus, for each Office 365 tenant a single OU exists in ExODS, with another one hosting any soft-deleted objects. Indeed, if one uses the Get-OrganizationalUnit cmdlet in Exchange Online, a glimpse at the underlying OU structure is exposed: Even though some of the individual Office 365 workloads, such as Exchange Online or SharePoint Online have their own AD instances at the backend, which in turn have their own OU hierarchy, we as customers have no way of modifying that hierarchy by say creating a new OU. In Azure AD however, no notion of OUs exists and instead a “flat hierarchy” is used. When a company starts using Office 365, the option exists to synchronize their on-premises AD with the cloud-based Azure Active Directory. Used as the building blocks of your organizational hierarchy, OUs greatly simplify some of the management tasks in AD, ensure policy enforcement via GPOs and enable granular rights delegation. It’s a common scenario to have all the users, groups and computers from a particular office, city or country placed in their own OU, which is then used as a single management unit. For decades now, admins have been using Organizational Units to conveniently organize the objects in their on-premises Active directory.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |