Merge pull request #176887 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/develop/scenario-web-app-call-api-app-configuration.md

@@ -104,7 +104,7 @@ Your web app will need to acquire a token for the downstream API. You specify it
      {
      // ...
      services.AddAuthentication(OpenIdConnectDefaults.AuthenticationScheme)
-             .AddMicrosoftIdentityWebApp(Configuration, Configuration.GetSection("AzureAd"))
+             .AddMicrosoftIdentityWebApp(Configuration, "AzureAd")
                .EnableTokenAcquisitionToCallDownstreamApi(new string[]{"user.read" })
                .AddInMemoryTokenCaches();
       // ...
@@ -134,7 +134,7 @@ If you want to call Microsoft Graph, *Microsoft.Identity.Web* enables you to dir
      {
      // ...
      services.AddAuthentication(OpenIdConnectDefaults.AuthenticationScheme)
-             .AddMicrosoftIdentityWebApp(Configuration, Configuration.GetSection("AzureAd"))
+             .AddMicrosoftIdentityWebApp(Configuration, "AzureAd")
                .EnableTokenAcquisitionToCallDownstreamApi(new string[]{"user.read" })
                   .AddMicrosoftGraph(Configuration.GetSection("GraphBeta"))
                .AddInMemoryTokenCaches();
@@ -540,4 +540,4 @@ def _build_msal_app(cache=None):
 
 At this point, when the user signs in, a token is stored in the token cache. Let's see how it's then used in other parts of the web app.
 
-[Remove accounts from the cache on global sign-out](scenario-web-app-call-api-sign-in.md)
+[Remove accounts from the cache on global sign-out](scenario-web-app-call-api-sign-in.md)

articles/active-directory/devices/hybrid-azuread-join-plan.md

@@ -27,6 +27,10 @@ By bringing your devices to Azure AD, you maximize your users' productivity thro
 
 If you have an on-premises Active Directory (AD) environment and you want to join your AD domain-joined computers to Azure AD, you can accomplish this by doing hybrid Azure AD join. This article provides you with the related steps to implement a hybrid Azure AD join in your environment. 
 
+> [!TIP]
+> SSO access to on-premises resources is also available to devices that are Azure AD joined. For more information, see [How SSO to on-premises resources works on Azure AD joined devices](azuread-join-sso.md).
+>
+
 ## Prerequisites
 
 This article assumes that you are familiar with the [Introduction to device identity management in Azure Active Directory](./overview.md).

articles/baremetal-infrastructure/workloads/oracle/oracle-baremetal-patching.md

@@ -18,6 +18,7 @@ Servers are delivered to customers with compatible versions. However, during OS/
 | --- | --- | --- | --- | --- |
 | Red Hat | RHEL 7.6 | 3.2.3i | 2.3.0.53 | 1.6.0.34 |
 | Red Hat | RHEL 7.6 | 4.1.1b | 2.3.0.53 | 1.6.0.34 |
+| Red Hat | RHEL 7.6 | 4.1.1b | 4.0.0.8  | 2.0.0.60 |
 
 ## Next steps
 

articles/governance/policy/toc.yml

@@ -396,8 +396,8 @@
       href: /answers/topics/azure-policy.html
     - name: Azure support ticket
       href: https://azure.microsoft.com/support/create-ticket/
-    - name: UserVoice
-      href: https://feedback.azure.com/forums/915958-azure-governance?category_id=345055
+    - name: Azure Governance Ideas
+      href: https://feedback.azure.com/d365community/forum/675ae472-f324-ec11-b6e6-000d3a4f0da0#
   - name: Videos
     items:
     - name: Governance YouTube Channel

articles/openshift/openshift-faq.yml

@@ -31,7 +31,7 @@ sections:
         answer: |
           The actual number of supported pods depends on an application’s memory, CPU, and storage requirements.
           
-          Azure Red Hat OpenShift 4.x has a 250 pod-per-node limit and a 100 compute node limit. This caps the maximum number of pods supported in a cluster to 250×100 = 25,000.
+          Azure Red Hat OpenShift 4.x has a 250 pod-per-node limit and a 60 compute node limit. This caps the maximum number of pods supported in a cluster to 250×60 = 15,000.
           
           Azure Red Hat OpenShift 3.11 has a 50 pod-per-node limit and a 20 compute node limit. This caps the maximum number of pods supported in a cluster to 50×20 = 1,000.
           

articles/security/fundamentals/measured-boot-host-attestation.md

@@ -15,7 +15,7 @@ This article describes how Microsoft ensures integrity and security of hosts thr
 
 ## Measured boot
 
-The [Trusted Platform Module](/windows/security/information-protection/tpm/trusted-platform-module-top-node) (TPM) is a tamper-proof, cryptographically secure auditing component with firmware supplied by a trusted third party. The boot configuration log contains hash-chained measurements recorded in it's Platform Configuration Registers (PCR) when the host last underwent the bootstrapping sequence. The following figure shows this recording process. Incrementally adding a previously hashed measurement to the next measurement’s hash and running the hashing algorithm on the union accomplishes hash-chaining.
+The [Trusted Platform Module](/windows/security/information-protection/tpm/trusted-platform-module-top-node) (TPM) is a tamper-proof, cryptographically secure auditing component with firmware supplied by a trusted third party. The boot configuration log contains hash-chained measurements recorded in its Platform Configuration Registers (PCR) when the host last underwent the bootstrapping sequence. The following figure shows this recording process. Incrementally adding a previously hashed measurement to the next measurement’s hash and running the hashing algorithm on the union accomplishes hash-chaining.
 
 ![Diagram that shows Host Attestation Service hash-chaining.](./media/measured-boot-host-attestation/hash-chaining.png)
 
@@ -54,4 +54,4 @@ To learn more about what we do to drive platform integrity and security, see:
 - [Secure boot](secure-boot.md)
 - [Project Cerberus](project-cerberus.md)
 - [Encryption at rest](encryption-atrest.md)
-- [Hypervisor security](hypervisor.md)
+- [Hypervisor security](hypervisor.md)