Cloud sync AD > Entra - custom attributes with cloud sync

Question

Hi,

We need to add several new attributes to our onprem AD schema and have these attributes synced to Entra ID. I've successfully added the new attributes in the onprem environment and it has replicated throughout our entire domain. This was completed around 18 hours ago.

I do not see the newly created attributes when attempting to create the attribute map in cloud sync, even though I do see a popup stating it is reading attributes from the environment.

What do I need to do to find our new custom attribute in the console? Is there a process I need to run to force the tool to refresh the schema? I'm unable to find any indication that I should do anything other than what I currently am.

Tom

Answer 1

Hi @Tom Anderson,

Thank you for contacting Q&A Forum. I would like to provide my findings and proposed solution:

Here’s how to get your new on-prem AD attributes to show up in the cloud-sync mapping UI—you need to force a schema refresh.

Azure AD Cloud Provisioning (cloud sync) By design the provisioning agent refreshes your on-prem schema every 24 hours—here’s how to do it immediately:

On each provisioning-agent VM, restart the “Microsoft Azure AD Connect Provisioning Agent” service.

Wait ~5 minutes for the agent to upload the updated schema.

In the Azure portal go to Entra ID → Provisioning → [Your on-prem target] → Attribute mappings and click Refresh schema at the top.

Your custom attribute will now appear in the list so you can add it to the mapping.

Reference:https://learn.microsoft.com/en-us/entra/identity/hybrid/cloud-sync/how-to-transformation#custom-attribute-mapping

Kindly let me know if this work for you and please let me know if you have any further questions.

If I have answered your question, please accept this answer as a token of appreciation and don't forget to give a thumbs up for "Was it helpful"!

Best regards,
Eric

Answer 2

You need to "refresh" the schema, this should be triggered by restarting the provisioning agent. If that doesn't help, you have to rerun the provisioning agent installation part.