Merge pull request #183053 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/azure-docs (branch master)

Author: huypub

articles/active-directory/devices/howto-vm-sign-in-azure-ad-linux.md

@@ -103,7 +103,7 @@ Ensure your client meets the following requirements:
 - TCP connectivity from the client to either the public or private IP of the VM (ProxyCommand or SSH forwarding to a machine with connectivity also works).
 
 > [!IMPORTANT]
-> SSH clients based on PuTTy do not support openSSH certificates and cannot be used to login with Azure AD openSSH certiicate-based authentication.
+> SSH clients based on PuTTy do not support openSSH certificates and cannot be used to login with Azure AD openSSH certificate-based authentication.
 
 ## Enabling Azure AD login in for Linux VM in Azure
 

articles/active-directory/governance/access-reviews-downloadable-review-history.md

@@ -55,6 +55,7 @@ The reports provide details on a per-user basis showing the following:
 | Element name | Description |
 | --- | --- |
 | AccessReviewId |	Review object id |
+| AccessReviewSeriesId |	Object id of the review series, if the review is an instance of a recurring review. If a one-time review, the value will be am empty GUID. |
 | ReviewType | Review types include group, application, Azure AD role, Azure role, and access package|
 |ResourceDisplayName | Display Name of the resource being reviewed |
 | ResourceId | Id of the resource being reviewed |

articles/active-directory/governance/deploy-access-reviews.md

@@ -157,13 +157,13 @@ Typical targets for review include:
 
 ### Who will create and manage access reviews?
 
-The administrative role required to create, manage, or read an access review depends on the type of resource being reviewed. The following table denotes the roles required for each resource type.
+The administrative role required to create, manage, or read an access review depends on the type of resource being reviewed. The following table denotes the roles required for each resource type. Custom roles with permission Microsoft.Authorization/* can create and manage reviews of any resource type, and custom roles with at least permissions Microsoft.Authorization/*/read can read reviews of any resource type.
 
 | Resource type| Create and manage access reviews (creators)| Read access review results |
 | - | - | -|
 | Group or application| Global administrator <p>User administrator<p>Identity Governance administrator<p>Privileged Role administrator (only does reviews for Azure AD role-assignable groups)<p>Group owner ([if enabled by an admin]( create-access-review.md#allow-group-owners-to-create-and-manage-access-reviews-of-their-groups-preview))| Global administrator<p>Global reader<p>User administrator<p>Identity Governance administrator<p>Privileged Role administrator<p>Security reader<p>Group owner ([if enabled by an admin]( create-access-review.md#allow-group-owners-to-create-and-manage-access-reviews-of-their-groups-preview)) |
 |Azure AD roles| Global administrator <p>Privileged Role administrator|  Global administrator<p>Global reader<p>User administrator<p>Privileged Role administrator<p> <p>Security reader |
-| Azure resource roles| Global administrator<p>Resource owner| Global administrator<p>Global reader<p>User administrator<p>Privileged Role administrator<p> <p>Security reader  |
+| Azure resource roles| User Access Administrator (for the resource)<p>Resource owner| User Access Administrator (for the resource)<p>Resource owner<p>Reader (for the resource) |
 | Access package| Global administrator<p>User administrator<p>Identity Governance administrator| Global administrator<p>Global reader<p>User administrator<p>Identity Governance administrator<p> <p>Security reader  |
 
 For more information, see [Administrator role permissions in Azure AD](../roles/permissions-reference.md).
@@ -442,4 +442,4 @@ For more advanced queries and analysis of access reviews, and to track changes a
 Learn about the following related technologies:
 
 * [What is Azure AD entitlement management?](entitlement-management-overview.md)
-* [What is Azure AD Privileged Identity Management?](../privileged-identity-management/pim-configure.md)
+* [What is Azure AD Privileged Identity Management?](../privileged-identity-management/pim-configure.md)

articles/postgresql/how-to-upgrade-using-dump-and-restore.md

@@ -97,7 +97,7 @@ pg_dumpall -r --host=mySourceServer --port=5432 --username=myUser --database=myS
 Edit the `roles.sql` and remove references of `NOSUPERUSER` and `NOBYPASSRLS` before restoring the content using psql in the target server:
 
 ```azurecli-interactive
-psql -f roles.sql --host=myTargetServer --port=5432 --username=myUser
+psql -f roles.sql --host=myTargetServer --port=5432 --username=myUser --dbname=postgres
 ```
 
 The dump script should not be expected to run completely without errors. In particular, because the script will issue CREATE ROLE for every role existing in the source cluster, it is certain to get a “role already exists” error for the bootstrap superuser like azure_pg_admin or azure_superuser. This error is harmless and can be ignored. Use of the `--clean` option is likely to produce additional harmless error messages about non-existent objects, although you can minimize those by adding `--if-exists`.

includes/site-recovery-configuration-and-scaleout-process-server-requirements.md

@@ -71,7 +71,7 @@ MYSQL | MySQL should be installed. You can install manually, or Site Recovery ca
 |
 
 > [!NOTE]
-> Upgrading MySql on the configuration server is not supported.
+> Upgrading MySQL on the configuration server is not supported.
 
 ## Sizing and capacity requirements