Merge pull request #91335 from MicrosoftDocs/master

10/10 PM Publish

Author: huypub

.openpublishing.redirection.json

@@ -9,7 +9,12 @@
       "source_path": "articles/azure-government/documentation-government-get-started-connect-with-vs.md",
       "redirect_url": "/azure/azure-government/documentation-government-welcome",
       "redirect_document_id": false
-    },
+    },    
+    {
+      "source_path": "articles/container-registry/container-registry-auth-aks.md",
+      "redirect_url": "/azure/aks/cluster-container-registry-integration",
+      "redirect_document_id": true
+    },    
     {
       "source_path": "articles/security/develop/security-code-analysis-install.md",
       "redirect_url": "/azure/security/develop/security-code-analysis-onboard",

articles/active-directory/develop/customize-webviews.md

@@ -22,7 +22,7 @@ ms.collection: M365-identity-device-management
 
 # How to: Customize browsers and WebViews for iOS/macOS
 
-A web browser is required for interactive authentication. On iOS, the Microsoft Authentication Library (MSAL) uses a system web browser by default (which might appear on top of your app) to do interactive authentication to sign in users. Using the system browser has the significant advantage of sharing the Single Sign ON (SSO) state with other applications and with web applications.
+A web browser is required for interactive authentication. On iOS, the Microsoft Authentication Library (MSAL) uses the system web browser by default (which might appear on top of your app) to do interactive authentication to sign in users. Using the system browser has the advantage of sharing the Single Sign ON (SSO) state with other applications and with web applications.
 
 You can change the experience by customizing the configuration to other options for displaying web content, such as:
 

articles/active-directory/develop/howto-v2-keychain-objc.md

@@ -22,7 +22,7 @@ ms.collection: M365-identity-device-management
 
 # Configure keychain
 
-When the [Microsoft Authentication Library for iOS and macOS](msal-overview.md) (MSAL) signs in a user, or refreshes a token, it tries to cache tokens in the keychain. By caching tokens in the keychain, MSAL can provide silent single sign-on (SSO) between multiple apps distributed by the same Apple developer. SSO is achieved via the keychain access groups functionality (see [Apple's documentation](https://developer.apple.com/documentation/security/keychain_services/keychain_items/sharing_access_to_keychain_items_among_a_collection_of_apps?language=objc))
+When the [Microsoft Authentication Library for iOS and macOS](msal-overview.md) (MSAL) signs in a user, or refreshes a token, it tries to cache tokens in the keychain. Caching tokens in the keychain allows MSAL to provide silent single sign-on (SSO) between multiple apps that are distributed by the same Apple developer. SSO is achieved via the keychain access groups functionality. For more information, see Apple's [Keychain Items documentation](https://developer.apple.com/documentation/security/keychain_services/keychain_items/sharing_access_to_keychain_items_among_a_collection_of_apps?language=objc).
 
 This article covers how to configure app entitlements so that MSAL can write cached tokens to iOS and macOS keychain.
 

articles/active-directory/develop/quickstart-v2-ios.md

@@ -263,7 +263,7 @@ self.applicationContext!.acquireTokenSilent(with: silentParams) { (result, error
 > |Where: ||
 > |---------|---------|
 > | `scopes` | Contains the scopes being requested (that is, `[ "user.read" ]` for Microsoft Graph or `[ "<Application ID URL>/scope" ]` for custom Web APIs (`api://<Application ID>/access_as_user`) |
-> | `account` | The account a token is being requested for. This quickstart is a single account application, if you want to build a multi-account app you'll need to define logic to identify which account to use for token requests `applicationContext.account(forHomeAccountId: self.homeAccountId)` |
+> | `account` | The account a token is being requested for. This quickstart is about a single account application. If you want to build a multi-account app you'll need to define logic to identify which account to use for token requests using `applicationContext.account(forHomeAccountId: self.homeAccountId)` |
 
 ## Next steps
 

articles/active-directory/develop/sso-between-adal-msal-apps-macos-ios.md

@@ -107,7 +107,7 @@ You can save this identifier to use in MSAL for account lookups with the `accoun
 
 If `homeAccountId` is not available, or you only have the displayable identifier, you can use ADAL's `userId` to lookup the account in  MSAL.
 
-In MSAL, first look up an account by `username` or `identifier`. Always use `identifier` for querying if you have it and only use `username` as a fallback. If account is found, use the account in the acquireTokenSilent calls.
+In MSAL, first look up an account by `username` or `identifier`. Always use `identifier` for querying if you have it, and only use `username` as a fallback. If the account is found, use the account in the `acquireTokenSilent` calls.
 
 Objective-C:
 

articles/active-directory/manage-apps/index.yml

@@ -7,10 +7,10 @@ metadata:
    title: Application management documentation
    description: Azure Active Directory provides secure and seamless access to cloud and on-premises applications. Plus, there's no need to manage passwords. Your end-users can sign in once to access Office 365 and thousands of other applications. Learn how to manage and deploy applications with our quickstarts, tutorials, and guidance.
    ms.service: active-directory
-   ms.subservice: manage-apps
+   ms.subservice: app-mgmt
    ms.workload: identity
    ms.topic: landing-page
-   ms.date: 08/16/2019
+   ms.date: 10/10/2019
    author: msmimart
    ms.author: mimart
    manager: celested

articles/active-directory/reports-monitoring/tutorial-azure-monitor-stream-logs-to-event-hub.md

@@ -39,7 +39,7 @@ To use this feature, you need:
 
 1. Sign in to the [Azure portal](https://portal.azure.com). 
 
-2. Select **Azure Active Directory** > **Activity** > **Audit logs**. 
+2. Select **Azure Active Directory** > **Monitoring** > **Audit logs**. 
 
 3. Select **Export Settings**.