accumulated many duplicate user and group attributes. Although this wouldn’t create an issue in Active Directory, the attributes had to be cleaned up to ensure successful synchronization with Azure AD. In an on-premises environment, duplicate aliases are acceptable, provided that they have unique suffixes after the at sign (@). However, all aliases in Office 365 must be unique for a given organization. Even if addresses have multiple unique suffixes, all aliases must be unique in the Simple Mail Transfer Protocol (SMTP) address. Before migration, the Microsoft IT team needed to resolve about 30,000 duplicates in the on-premises directory. This project took six weeks, but the migration would have failed without it. As a best practice, before you migrate to Azure AD, make sure that alias values are unique within your Active Directory. Azure AD will not accept duplicate values. Any synchronization operation that tries to write a duplicate alias value to the directory will fail. For details about resolving duplicate attributes, see . Log all writes and errors To support forensics, security auditing, and tech support, it’s a good idea to log every write that the automation application makes to Azure AD and log every error. Logging helps you track performance, troubleshoot problems, and research issues when users contact the help desk for assistance. Account for throttling in your code Azure AD uses throttling to ensure that no single tenant can cause issues with the entire service. To handle this potential for throttling, include code in your automation application that looks for a throttling error and pauses automation for five minutes before restarting. Search on unique attributes When you search Azure AD for users, search on the UPN or some other unique attribute. For example, if the display name is used instead of the UPN, results could include multiple users who have the same name, whereas using the UPN or some other unique attribute will return only a single user. Resources © 2016 Microsoft Corporation. All rights reserved. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.
accumulated many duplicate user and group attributes. Although this wouldn’t create an issue in Active Directory, the attributes had to be cleaned up to ensure successful synchronization with Azure AD. In an on-premises environment, duplicate aliases are acceptable, provided that they have unique suffixes after the at sign (@). However, all aliases in Office 365 must be unique for a given organization. Even if addresses have multiple unique suffixes, all aliases must be unique in the Simple Mail Transfer Protocol (SMTP) address. Before migration, the Microsoft IT team needed to resolve about 30,000 duplicates in the on-premises directory. This project took six weeks, but the migration would have failed without it. As a best practice, before you migrate to Azure AD, make sure that alias values are unique within your Active Directory. Azure AD will not accept duplicate values. Any synchronization operation that tries to write a duplicate alias value to the directory will fail. For details about resolving duplicate attributes, see . Log all writes and errors To support forensics, security auditing, and tech support, it’s a good idea to log every write that the automation application makes to Azure AD and log every error. Logging helps you track performance, troubleshoot problems, and research issues when users contact the help desk for assistance. Account for throttling in your code Azure AD uses throttling to ensure that no single tenant can cause issues with the entire service. To handle this potential for throttling, include code in your automation application that looks for a throttling error and pauses automation for five minutes before restarting. Search on unique attributes When you search Azure AD for users, search on the UPN or some other unique attribute. For example, if the display name is used instead of the UPN, results could include multiple users who have the same name, whereas using the UPN or some other unique attribute will return only a single user. Resources © 2016 Microsoft Corporation. All rights reserved. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.
5721_Automating_licensing_for_Office_365_in_a_hybrid_environment_TCS.docx