We have a multi-forest AD Connect setup and have added a new attribute first in local AD of 1 forest/directory only and then a custom Directory extension attributes for the same in AD Connect(guess its for everyone now). The expectation is that as our different countries/directories will keep adding this new attribute, it'll require just a Refresh Schema on AD Connect from hereon. Please correct if this requires more actions on our part.
More importantly, the new attribute is not visible list of Source attributes under Mappings in Azure AD >>> Enterprise Apps >>> SCIM Provisioning. We can find the attribute and its value in user's extension attribute once checked in PowerShell(screenshot attached). In fact, we can't see any custom AAD Directory Extensions added through AD Connect in SCIM Provisioning, only the default ones are listed. Please help us understand what we are missing here.
We also have a test tenant synced with our test on-premise lab and that shows all AAD Extension attributes without any issue. No extra steps were followed while configuring the same there.
