Azure Active Directory

  1. The Remove-MsolDomain cmdlet is used to delete a domain from Microsoft Azure Active Directory. The domain being deleted must ...
  2. The Remove-MsolForeignGroupToRole cmdlet is used to remove the specified security group from the specified role in this tenant. ...
  3. The Remove-MsolGroupMember cmdlet is used to remove a member from a security group. This member can be either a user or a ...
  4. The Remove-MsolServicePrincipalCredential cmdlet can be used to remove a credential key from a service principal in the case ...
  5. The Remove-MsolSettings cmdlet can be used to remove a directory setting. The credential to be removed is identified by its ...
  6. The Remove-MsolUser cmdlet is used to remove a user from Microsoft Azure Active Directory. This cmdlet will delete the user, ...
  7. The renewal request failed because profile template {0} changed since the last time you enrolled. Instead of renewing, you ...
  8. The report has been queued. The report will be available for download on the %{link} page when it is finished processing. ...
  9. The reporting initial synchronization job has encountered a request which contains a change to an attribute that is no longer ...
  10. The request '{0}' from '{1}' cannot be approved or rejected because it was not received from the following authorized sender(s): ...
  11. The request has completed but no certificates were written to the FIM CM database. Please contact your Administrator to ensure ...
  12. The Request that created this Request. If this Request was not created by a workflow, this attribute will not have a value. ...
  13. The request to create role assignment '{0}' is not valid. Role assignment scope '{1}' must match the scope specified on the ...
  14. The request to create the role definition '{0}' is not valid. Assignable scope values must contain at least 2 resource path ...
  15. The request to create the roleDefinition '{0}' is not valid. At least one of the scopes that are available for assignment ...
  16. The request to the Rights Management service to get a migration URL failed. If you have continued problems, see http://g ...
  17. The request to the Rights Management service to get tenant user on-boarding policy failed. If you have continued problems, ...
  18. The request to the Rights Management service to set a migration URL failed. Verify that the format of the domain entered ...
  19. The requested update failed. The size of the object is too big. Please ensure large attributes such as proxyAddresses do ...
  20. The requested user update failed. The update has failed too many times. Please review previous errors reported for this user ...
  21. The requestor has specified that the subscription be retained within their organization. Please contact the requestor and ...
  22. The Resource Synchronization Service has timed out waiting for the completion of any exports from the Forefront Identity ...
  23. The resource type in the external system to scope the flow to when the Metaverse reference to flow is connected to multiple ...
  24. The resource type of a resource. This attribute is assigned its value when the resource is created in the FIM service database ...
  25. The results (user names and temporary passwords for users who have them) will be displayed on the next page. You can also ...
  26. The revocation status of the certificate or one of the certificates in the certificate chain is either off-line or stale. ...
  27. The Rights Management administration log was not generated. You can retry this action. If you have continued problems, see ...
  28. The Rights Management IPC v3 service has been successfully disabled although additional configuration of other services might ...
  29. The Rights Management IPC v3 service has been successfully enabled although additional configuration of other services might ...
  30. The Rights Management IPC v3 service service was not enabled. You can retry this action. If you have continued problems, ...
  31. The Rights Management IPC v3 service was not disabled. You can retry this action. If you have continued problems, see ht ...
  32. The Rights Management service could not complete the operation as the certificate chain was not trusted. Visit the Troubleshooting ...
  33. The Rights Management service could not complete the operation as the certificate chain was not trusted. Visit the Troubleshooting ...
  34. The Rights Management service could not determine the connection URI to be used for administration. You can retry this action. ...
  35. The Rights Management service failed to authenticate the user. Verify that the user name and password you are using are correct ...
  36. The Rights Management service failed to delete template with ID {0}. Verify that the template exists by using the Get-AadrmTemplate ...
  37. The Rights Management service failed to download usage logs. You can retry this action. If you have continued problems, see ...
  38. The Rights Management service failed to get usage log storage account. You can retry this action. If you have continued problems, ...
  39. The Rights Management service failed to load the the Microsoft Online Services Sign-In Assistant. Verify that it is installed ...
  40. The Rights Management service failed to remove {0} from the list of administrators. Verify that the user or group exists ...
  41. The Rights Management service failed to remove {0} from the list of super users. Verify that the user exists in the list ...
  42. The Rights Management service failed to return a list of role based administrators. You can retry this action. If you have ...
  43. The Rights Management service failed to return a list of super users. You can retry this action. If you have continued problems, ...
  44. The Rights Management service failed to return its configuration. You can retry this action. If you have continued problems, ...
  45. The Rights Management service failed to return its current IPCv3 service state. You can retry this action. If you have continued ...
  46. The Rights Management service failed to return its current state. You can retry this action. If you have continued problems, ...
  47. The Rights Management service failed to return the current state of the document tracking feature. You can retry this action. ...
  48. The Rights Management service failed to return the current state of the super user feature. You can retry this action. If ...
  49. The Rights Management service failed to return the current state of the usage log feature. You can retry this action. If ...
  50. The Rights Management service failed to return the last value of the counter for the usage log feature. You can retry this ...
  51. The Rights Management service failed to save the administration log. Verify that the log file path is correct and that you ...
  52. The Rights Management service failed to set the state of the document tracking feature. You can retry this action. If you ...
  53. The Rights Management service failed to validate access to your account, this could be due to internal issue, please try ...
  54. The Rights Management service has been successfully disabled although additional configuration of other services might be ...
  55. The Rights Management service has been successfully enabled although additional configuration of other services might be ...
  56. The Rights Management service is unable to authenticate the user account %@ due to an incorrect Identity configuration. Contact ...
  57. The Rights Management service received an invalid certificate from the client. Close any packet-level inspection application ...
  58. The Rights Management service request {0} for {1} failed because the user is not authorized. The correlation ID for this ...
  59. The Rights Management service was not disabled. You can retry this action. If you have continued problems, see http://go ...
  60. The Rights Management service was not enabled. You can retry this action. If you have continued problems, see http://go. ...
  61. The RMS sharing app can't be used to share High Business Impact (HBI) data outside of Microsoft. If this is HBI data, press ...
  62. The RMS software used by this application needs to be updated. Contact technical support for this application, or your administrator, ...
  63. The role assignment {0} request is not valid. The request does not contain the role assignment or the role assignment properties. ...
  64. The role definition '{0}' request is not valid. The request does not contain the role definition or the role definition properties. ...
  65. The role definition '{0}' request is not valid. The Role definition type value '{1}' is not supported. The supported values ...
  66. The role to add members to. Only users can be added to a role (adding a security group is not supported). Either RoleName ...
  67. The root domain of a subdomain must be configured first. Please configure root domain {0} before configuring subdomain {1}. ...
  68. The sample backend service was written as an ASP.Net Core web API. .Net Core ships with a library for performing JSON Web ...
  69. The search criteria you have selected returned more then 2000 results. Please refine your criteria, or choose SortField=None ...
  70. The search string to be used in the search. Only objects with DirSyncProvisioningErrors due to a PropertyConflict returned ...
  71. The section, Microsoft.ResourceManagement.WebServices.Client.Configuration.ResourceManagementClientSection, is missing from ...
  72. The security code you entered does not match the code we sent, or it has expired. This could happen because you clicked on ...
  73. The security policy used by the Microsoft Azure Active Directory Module was not accepted by the server. Contact Technical ...
  74. The selected SSL certificate contains multiple subject names. Select the subject name that matches the endpoint used by the ...
  75. The sender has protected the attachment(s) with Microsoft Rights Management. For first time use, see these instructions . ...