No provisioning group assignments could be retrieved using the supplied credentials, which may be because no workers have been assigned to provisioning groups. You may choose to continue, but although workers may be provisioned as users with Microsoft Azure Active Directory, they will not be assigned to any groups. If you were to assign your workers to at least one Workday provisioning group, then they would be assigned to a group with the same name in Azure Active Directory, which would be created if it did not already exist. Then licences for self-service password reset could be assigned to that group, which would allow the newly-provisioned users to log on to Azure Active Directory.
No common consistency points found across replicating volumes. {protectionGroupVMConsistencyErrorId}| View Details|{prot ...
No credit remains for the '{0}' subscription. The subscription is now disabled. Please contact your account administrator. ...
No databases are associated with this server. If you delete this server, your databases on other servers will remain intact. ...
No DRAs were found on site containing protection group '{0}'. Do you want to remove protection settings only from Azure Site ...
No provisioning group assignments could be retrieved using the supplied credentials, which may be because no workers have ...
No provisioning groups could be retrieved using the supplied credentials, which may be because no provisioning groups exist. ...
No records available for the given batch. To refresh the report, click on refresh command below. If this problem persists, ...
No storage classifications are currently defined. Before mapping, create storage classifications on source and target VMM ...
No verified custom domains. To enable automatic provisioning of users to a Google Apps domain, that domain must be a verified ...