戻る
-
タイトル
Known issues and limitations as of June 2017 -
説明
This solution outlines the known issues and limitations of On Demand Backup and Recovery for Azure AD as of March 2017 release. -
原因
-
対策
Below are two known issues and limitations within the current (June 2017) release of On Demand Backup and Recovery for Azure AD:- If you restore two groups which are members of the third group which was deleted, the third groupcan be duplicated after the restore operation. This issue is applied only to non-Office Groupswhich support nesting - Issue ID #18Workaround: To avoid this issue, the user needs either to restore groups one by one (order is notimportant) or restore all of them at once.
- Recovery for Azure Active Directory does not back up and does not store user passwords - Issue ID #129
- Recovery for Azure Active Directory does not support restore of Contact objects. - Issue ID #130
- Recovery for Azure Active Directory does not support restore of dynamic groups (the feature of Azure AD Premium). If a user tries to restore dynamic group, the application will restore it as nondynamic - Issue ID #120 with all explicitly applied members.
- The following error is shown "Failed to add <user_name> to group All Users. Status: 403, Code: Authorization_RequestDenied" if you try to restore a user in Azure AD Premium that is a member of the All Users dynamic group. The similar error will be shown if the user is a member of any other dynamic group. - Issue ID #126 Workaround: To avoid this error, please restore only required properties and membership information using the Differences view.
- Non-explicit permissions for all cloud services (such as Exchange Online, One Drive, SharePoint Online, etc) are lost after restore of permanently deleted users or groups due to the Object ID attributes were changed. - Issue ID #127
- Recovery for Azure Active Directory does not restore Applications for users and groups. - Issue ID #133
- Recovery for Azure Active Directory does not restore the Directory role attribute for users. - Issue ID #134
- Restore of on-premises objects which are synchronized by Azure AD Connect is not supported except for cloud-only properties: Licenses, Block Sign In, membership in Office Groups. - Issue ID #135 Workaround: An object can be restored if Azure AD Connect is disabled for it NOTE: Cloud-only objects can be restored (Office Groups, B2B users, other cloud-only users - objects which are not in the scope of Azure AD Connect).
- Restore of changed user mail attributes such as mail, proxyAddress, targetAddress is not supported. These attributes are restored correctly if you restore the deleted object from Recycle Bin. - Issue ID #136
- Recovery for Azure Active Directory does not restore user's Photo (thumbnailPhoto attribute). - Issue ID #138
- Recovery for Azure Active Directory does not restore Contact Authentication attributes: Authentication Email, Alternate Authentication Email, Authentication Phone, Alternate Authentication Phone. - Issue ID #136
- Backup and restore of Azure Active Directory B2C is not supported. In this case, the following error is shown in the Backup task: "Failed backup. Message: Execution stopped unexpectedly. BackupException: Get bad status: 400, response: {odata.error:{code:Request_UnsupportedQuery,message:{lang:en,value:Change enumeration is not supported for requested tenant.}}}". - Issue ID #140
- Recovery for Azure Active Directory does not restore multi-factor authentication settings for users. - Issue ID #141
- Recovery for Azure Active Directory does not restore Distribution List members with the error "Status: 400, Code: Request_BadRequest. Details: Unable to update the specified properties for objects that have originated within an external service". - Issue ID #174
- Backup and restore of device objects registered in Azure Active Directory is not supported. - Issue ID #179
- The Differences view shows objects that were permanently deleted before the backup creation (these objects should not be shown). Restore of these objects with GUIDs as names from the Difference view fails with Internal Error. Workaround: If you need to restore exactly these objects with original GUIDs, you should unpack the previous backup and try to find the objects in it - Issue ID #182