This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 60%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMC%3C/text%3E%3C/svg%3E)
We recently noticed that our Azure application for provisioning is skipping accounts with the message "this object is not assigned to the application." We verified the accounts are in the group that is configured in the scoping section. This issue just started recently.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(307.2, 26%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVK%3C/text%3E%3C/svg%3E)
Its difficult to get the context about this issue from this error message. Can you please elaborate a little more on this. But, if I am getting it correctly you are getting this error with the authorization, correct? If so please create an ICM on us or provide more details such as correlationId, resource id so that we can investigate this issue?
It may have something to do with the authorizations for your managed application. But, we will need more details as mentioned in above comment to investigate the issue in detail.
We were able to figure out the issue. At some point a change was made to the sync settings in AAD sync. The change stopped syncing an attribute that we using in the scoping options. The strange thing is that the logs did not show a false report for that attribute scope. Adding the attribute back into the sync fixed the issue.