Your videos are really excellent thank you so much for your hard work on these! Please keep them up I love the idea of knowing concepts before hands on I fully agree with this approach for learning!
Thank you. I needed to know how this works, because we use custom properties for a dynamic device group to scope scope tags from Intune that Service Desks can see only devices they are responsible for :)
This video was so helpful. Thank you for this video. In my case the created custom attribute is not showing in the Directory extensions (In the ADConnect) to select. Any suggestions please??
In this powershell command C:\> Set-AzureADUserExtension -ObjectId $User.ObjectId -ExtensionName extension_e5e29b8a85d941eab8d12162bd004528_extensionAttribute8 -ExtensionValue "New Value", How to get the exact Extension name from the Azure AD ?
Hi Team, I need to enable location AD attribute to sync as an extensions attribute, in this list of available attributes its showing as Location (Group) [string], can you confirm if this the correct one to be used as am seeing you are selecting a attribute which has (user) [string]. Am unable to find difference between group and user listed near the attributes
Hello Arun, I would suggest not to choose group [string], as it is related to group object, check for any other attributes, use any extension attribute.
@@ConceptsWork thank you after Refreshing the schema in Azure AD connect I found location (user) [string]. Now I have one more issue when I ran this config change health agent failed to register and test-azureadconnect -role Sync is saying invalid credentials in steps 2 , any thoughts on this ?
Hello, first of all I appreciate your video that was so helpful but I have a query in Azure AD Connect. We all knows that when user is sync from local AD , every changes we have to made in user, we can only make through on-premises AD exclude UserPrinciplename. We can change through from local AD and online as well using set-msoluserprinciplename. So my query is if someone change upn from local ad and after few minutes before completing the sync cycle someone change that too from online. Then which change will be replicated once the sync cycle will complete.
Yes, the change will be replicated provided immutable id is same. Changing upn from cloud is not recommended as it is used as a method to perform hard match.
Extended schema attribute not visible to Directory extension console in AAD, though its visible in user property. Please suggest. Dropped you an email along with screenshots.
You need to refresh the schema on Azure AD Connect Wizard, refreshing the schema will recreate the synchronization rules (nothing to worry), once you click on the final screen, click Configure. It will automatically start the Full Import on all the connectors, then Full Sync to Metaverse and then export on all the connectors. Now, you open the Azure AD Connect wizard again and follow the steps explained by Conceptswork.
thanks for this video, i will like to know if it's possible to see this attribute under the User properties in Azure AD?
Your videos are really excellent thank you so much for your hard work on these! Please keep them up I love the idea of knowing concepts before hands on I fully agree with this approach for learning!
Glad you like them!
Thank you. I needed to know how this works, because we use custom properties for a dynamic device group to scope scope tags from Intune that Service Desks can see only devices they are responsible for :)
Glad it was helpful!
Excellent video, thank you!
Hi, if the custom attributes which are created on the on-host premises are not showing in the Azure ad connect, what should I try to fix it.
nice way of explanation
thanks a lot man, you saved my day.
This video was so helpful. Thank you for this video. In my case the created custom attribute is not showing in the Directory extensions (In the ADConnect) to select. Any suggestions please??
Thank you fro the execllent video.How can the custom attribute be used in Exchange Online to create a Dynamic Distribution Group?
Hi, How you created the Custom attribute and could you please show that ?
You are amazing.
How to see or export extensionAttribute1-15 through Azure AD for all users
How did you create the attribute in the attribute editor under user properties? which is conceptsworkemployeetype.
social.technet.microsoft.com/wiki/contents/articles/20319.how-to-create-a-custom-attribute-in-active-directory.aspx
Thank you so much
You're most welcome
In this powershell command C:\> Set-AzureADUserExtension -ObjectId $User.ObjectId -ExtensionName extension_e5e29b8a85d941eab8d12162bd004528_extensionAttribute8 -ExtensionValue "New Value",
How to get the exact Extension name from the Azure AD ?
Hi Team,
I need to enable location AD attribute to sync as an extensions attribute, in this list of available attributes its showing as Location (Group) [string], can you confirm if this the correct one to be used as am seeing you are selecting a attribute which has (user) [string]. Am unable to find difference between group and user listed near the attributes
Hello Arun, I would suggest not to choose group [string], as it is related to group object, check for any other attributes, use any extension attribute.
@@ConceptsWork thank you after Refreshing the schema in Azure AD connect I found location (user) [string]. Now I have one more issue when I ran this config change health agent failed to register and test-azureadconnect -role Sync is saying invalid credentials in steps 2 , any thoughts on this ?
Hello, first of all I appreciate your video that was so helpful but I have a query in Azure AD Connect.
We all knows that when user is sync from local AD , every changes we have to made in user, we can only make through on-premises AD exclude UserPrinciplename. We can change through from local AD and online as well using set-msoluserprinciplename. So my query is if someone change upn from local ad and after few minutes before completing the sync cycle someone change that too from online. Then which change will be replicated once the sync cycle will complete.
Yes, the change will be replicated provided immutable id is same.
Changing upn from cloud is not recommended as it is used as a method to perform hard match.
Extended schema attribute not visible to Directory extension console in AAD, though its visible in user property. Please suggest. Dropped you an email along with screenshots.
You need to refresh the schema on Azure AD Connect Wizard, refreshing the schema will recreate the synchronization rules (nothing to worry), once you click on the final screen, click Configure. It will automatically start the Full Import on all the connectors, then Full Sync to Metaverse and then export on all the connectors.
Now, you open the Azure AD Connect wizard again and follow the steps explained by Conceptswork.