Question
You have an on-premises Active Directory Domain Services (AD DS) domain that syncs with Azure AD.
You deploy an app that adds custom attributes to the domain.
From Azure Cloud Shell, you discover that you cannot query the custom attributes of users.
You need to ensure that the custom attributes are available in Azure AD.
Which task should you perform from Microsoft Azure Active Directory Connect first?
- A. Configure device options
- B. Manage federation
- C. Customize synchronization options
- D. Refresh directory schema Correct
Explanation
Azure AD Connect caches the on-premises AD DS schema when it is installed, so attributes that an app adds to the schema later are not visible to it. The first task is Refresh directory schema, which reads the updated schema so the new custom attributes become available in the sync configuration. After that, you run Customize synchronization options and select the attributes on the Directory extensions page so they are synchronized to Azure AD. Configure device options handles hybrid device join and writeback, and Manage federation handles AD FS; neither makes new schema attributes available.
