API Driven Inbound Provisioning Service not populating Email field

Question

The sample bulk upload file contains

        "emails": [
          {
            "value": "******@contoso.com",
            "type": "work",
            "primary": true
          }
        ]

The default attribute mapping maps emails[type eq "work"].value to mail attribute.

However, the mail attribute value is not populated during provisioning.

Answer 1

@Mithunkumar Chopda Apologies for the delayed response, Regarding your above mentioned query - I am trying this integration directly with Entra ID, no on-prem involved even though customer's topology involves on-prem to Entra ID sync. In my scenario, the Identity can use personal email and I need to populate it in Email field.

If you want to populate personal email, you need to populate the same in other mails attribute of user.

Reference below screenshot:

How this can be achieved is via configuring attribute mappings like below:

Also refer to this article on how mail attribute is calculated for the user and why license is needed (as mentioned by Danny in his above answer) - https://learn.microsoft.com/en-us/troubleshoot/azure/active-directory/proxyaddresses-attribute-populate

Hope this clarifies your ask, apologies once again for the delayed response.

Let me know if you have any further questions, feel free to post back.

Please remember to "Accept Answer" if answer helped, so that others in the community facing similar issues can easily find the solution.

Answer 2

@Mithunkumar Chopda Thank you for reaching out to us, As I understand you have query on API Driven Inbound Provisioning Service not populating Email field.

Similar issue has been discussed here - https://stackoverflow.com/questions/76763662/is-microsoft-azure-misusing-the-scim-rfc-emailstype-eq-work-value-eq-foo where one of our PM has answered this post, hope this information helps you.

Let me know if you have any further questions, feel free to post back.

Answer 3

Assuming you are targeting Entra ID/Azure AD, at this time, the mail attribute cannot be written to via either the inbound provisioning API or any of our inbound HR provisioning integrations. This will be managed by Exchange Online if/when an Exchange license is activated on the user, at which point the email related attributes will be populated by the Exchange Online service.