Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

New-MigrationBatch doesn't honor RBAC management scope in Exchange Server 2019 and 2016


View products that this article applies to.

Symptoms

Consider the following scenario in a Microsoft Exchange Server 2019 or Exchange Server 2016 environment:
  • You create a RBAC management scope with DataBase write scope.
  • Apply the scope to a user.
  • The user runs the New-MigrationBatch PowerShell command with a database that is out of that scope in the TargetDatabases parameter.
In this scenario, the command runs successfully. 

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. 

↑ Back to the top


Resolution

To fix this issue, install one of the following updates:
For Exchange Server 2019, install the Cumulative Update 1 for Exchange Server 2019 or a later cumulative update for Exchange Server 2019.
For Exchange Server 2016, install the Cumulative Update 12 for Exchange Server 2016 or a later cumulative update for Exchange Server 2016.

↑ Back to the top


References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top


Keywords: kbHotfixAuto, CI97248, kb, kbfix, kbqfe, new-migrationbatch doesn't honor rbac scope

↑ Back to the top

Article Info
Article ID : 4488080
Revision : 11
Created on : 2/12/2019
Published on : 2/12/2019
Exists online : False
Views : 367