Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into release-sf-7.1

Author: v-alje

.openpublishing.redirection.json

@@ -345,6 +345,17 @@
       "redirect_url": "/azure/machine-learning/data-science-virtual-machine/dsvm-tools-languages",
       "redirect_document_id": true
     },
+    {
+      "source_path": "articles/machine-learning/data-science-virtual-machine/reference-centos-vm.md",
+      "redirect_url": "/azure/machine-learning/data-science-virtual-machine/reference-deprecation",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/machine-learning/data-science-virtual-machine/linux-dsvm-intro.md",
+      "redirect_url": "/azure/machine-learning/data-science-virtual-machine/reference-deprecation",
+      "redirect_document_id": true
+    },
+    
     {
       "source_path": "articles/machine-learning/service/how-to-understand-accuracy-metrics.md",
       "redirect_url": "/azure/machine-learning/service/how-to-understand-automated-ml",
@@ -4055,11 +4066,21 @@
       "redirect_url": "/azure/azure-government/documentation-government-welcome",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/azure-government/documentation-government-k8.md",
+      "redirect_url": "/azure/azure-government",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/azure-portal/resource-group-portal-linked-resources.md",
       "redirect_url": "/azure/azure-portal/azure-portal-dashboards",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/azure-resource-manager/templates/template-tutorial-create-linked-templates.md",
+      "redirect_url": "/azure/azure-resource-manager/templates/deployment-tutorial-linked-template",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/azure-resource-manager/templates/template-tutorial-create-encrypted-storage-accounts.md",
       "redirect_url": "/azure/azure-resource-manager/templates/template-tutorial-use-template-reference",
@@ -7586,7 +7607,7 @@
     },
     {
       "source_path": "articles/azure-functions/functions-add-output-binding-storage-queue-python.md",
-      "redirect_url": "/azure/azure-functions/functions-add-output-binding-storage-queue-cli.md?pivots=programming-language-python",
+      "redirect_url": "/azure/azure-functions/functions-add-output-binding-storage-queue-cli?pivots=programming-language-python",
       "redirect_document_id": false
     },
     {

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

@@ -84,7 +84,7 @@ Use the following table to get an overview of the steps that are required for yo
 | Configure service connection point | ![Check][1] | ![Check][1] | ![Check][1] |
 | Set up issuance of claims |     | ![Check][1] | ![Check][1] |
 | Enable non-Windows 10 devices |       |        | ![Check][1] |
-| Verify joined devices | ![Check][1] | ![Check][1] | [Check][1] |
+| Verify joined devices | ![Check][1] | ![Check][1] | ![Check][1] |
 
 ## Configure a service connection point
 

articles/active-directory/manage-apps/application-proxy-configure-single-sign-on-on-premises-apps.md

@@ -71,14 +71,14 @@ Before you can provide SSO for on-premises applications, you need to enable Appl
 
 2. In the **Set up Single Sign-On with SAML** page, go to the **Basic SAML Configuration** heading and select its **Edit** icon (a pencil). Make sure the **External URL** you configured in Application Proxy is populated in the **Identifier**, **Reply URL**, and **Logout URL** fields. These URLs are required for Application Proxy to work correctly. 
 
-3. Edit the **Reply URL** configured earlier so that its domain is reachable by Application Proxy. For example, if your **External URL** is `https://contosotravel-f128.msappproxy.net` and the original **Reply URL** was `https://contosotravel.com/acs`, you'll need to update the original **Reply URL** to `https://contosotravel-f128.msappproxy.net/acs`. 
+3. Edit the **Reply URL** configured earlier so that its domain reachable on the internet via Application Proxy. For example, if your **External URL** is `https://contosotravel-f128.msappproxy.net` and the original **Reply URL** was `https://contosotravel.com/acs`, you'll need to update the original **Reply URL** to `https://contosotravel-f128.msappproxy.net/acs`.
 
     ![Enter basic SAML configuration data](./media/application-proxy-configure-single-sign-on-on-premises-apps/basic-saml-configuration.png)
 
 
 4. Select the checkbox next to the updated **Reply URL** to mark it as the default.
 
-   * If the required **Reply URL** is already listed, mark this **Reply URL** as default and delete the previously configured **Reply URL**.
+   * Aftering marking the required **Reply URL** as default, you can also delete the previously configured **Reply URL** that used the internal URL.
 
    * For an SP-initiated flow, make sure the back-end application specifies the correct **Reply URL** or Assertion Consumer Service URL for receiving the authentication token.
 

articles/active-directory/users-groups-roles/linkedin-integration.md

@@ -21,21 +21,22 @@ You can allow users in your organization to access their LinkedIn connections wi
 
 > [!IMPORTANT]
 > The LinkedIn account connections setting is currently being rolled out to Azure AD organizations. When it is rolled out to your organization, it is enabled by default.
-> 
+>
 > Exceptions:
+>
 > * The setting is not available for customers using Microsoft Cloud for US Government, Microsoft Cloud Germany, or Azure and Office 365 operated by 21Vianet in China.
 > * The setting is off by default for tenants provisioned in Germany. Note that the setting is not available for customers using Microsoft Cloud Germany.
 > * The setting is off by default for tenants provisioned in France.
 >
-> Once LinkedIn account connections are enabled for your organization, the account connections work after users consent to apps accessing company data on their behalf. For information about the user consent setting, see [How to remove a user’s access to an application](https://docs.microsoft.com/azure/active-directory/application-access-assignment-how-to-remove-assignment).
+> Once LinkedIn account connections are enabled for your organization, the account connections work after users consent to apps accessing company data on their behalf. For information about the user consent setting, see [How to remove a user's access to an application](https://docs.microsoft.com/azure/active-directory/application-access-assignment-how-to-remove-assignment).
 
 ## Enable LinkedIn account connections in the Azure portal
 
 You can enable LinkedIn account connections for only the users you want to have access, from your entire organization to only selected users in your organization.
 
 1. Sign in to the [Azure AD admin center](https://aad.portal.azure.com/) with an account that's a global admin for the Azure AD organization.
 1. Select **Users**.
-1. On the **Users** blade, select **User settings**.
+1. On the **Users** page, select **User settings**.
 1. Under **LinkedIn account connections**, allow users to connect their accounts to access their LinkedIn connections within some Microsoft apps. No data is shared until users consent to connect their accounts.
 
     * Select **Yes** to enable the service for all users in your organization
@@ -50,25 +51,22 @@ You can enable LinkedIn account connections for only the users you want to have
 > LinkedIn integration is not fully enabled for your users until they consent to connect their accounts. No data is shared when you enable account connections for your users.
 
 ### Assign selected users with a group
-We have replaced the ‘Selected’ option that specifies a list of users with the option to select a group of users so that you can enable the ability to connect LinkedIn and Microsoft accounts for a single group instead of many individual users. If you don’t have LinkedIn account connections enabled for selected individual users, you don’t need to do anything. If you have previously enabled LinkedIn account connections for selected individual users, you should:
+
+We have replaced the 'Selected' option that specifies a list of users with the option to select a group of users so that you can enable the ability to connect LinkedIn and Microsoft accounts for a single group instead of many individual users. If you don't have LinkedIn account connections enabled for selected individual users, you don't need to do anything. If you have previously enabled LinkedIn account connections for selected individual users, you should:
 
 1. Get the current list of individual users
 1. Move the currently enabled individual users to a group
 1. Use the group from the previous as the selected group in the LinkedIn account connections setting in the Azure AD admin center.
 
 > [!NOTE]
-> Even if you don’t move your currently selected individual users to a group, they can still see LinkedIn information in Microsoft apps.
+> Even if you don't move your currently selected individual users to a group, they can still see LinkedIn information in Microsoft apps.
 
-### Get the current list of selected users
+### Move currently selected users to a group
 
+1. Create a CSV file of the users who are selected for LinkedIn account connections.
 1. Sign into Microsoft 365 with your administrator account.
-1. Go to https://linkedinselectedusermigration.azurewebsites.net/. You will see list of users who are selected for LinkedIn account connections.
-1. Export the list to a CSV file.
-
-### Move the currently selected individual users to a group
-
-1. Launch PowerShell
-1. Install Azure AD module by running `Install-Module AzureAD`
+1. Launch PowerShell.
+1. Install the Azure AD module by running `Install-Module AzureAD`
 1. Run the following script:
 
   ``` PowerShell

articles/app-service/environment/app-service-app-service-environment-control-inbound-traffic.md

@@ -27,10 +27,10 @@ Before locking down inbound network traffic with a network security group, it is
 
 The following is a list of ports used by an App Service Environment. All ports are **TCP**, unless otherwise clearly noted:
 
-* 454:  **Required port** used by Azure infrastructure for managing and maintaining App Service Environments via SSL.  Do not block traffic to this port.  This port is always bound to the public VIP of an ASE.
-* 455:  **Required port** used by Azure infrastructure for managing and maintaining App Service Environments via SSL.  Do not block traffic to this port.  This port is always bound to the public VIP of an ASE.
+* 454:  **Required port** used by Azure infrastructure for managing and maintaining App Service Environments via TLS.  Do not block traffic to this port.  This port is always bound to the public VIP of an ASE.
+* 455:  **Required port** used by Azure infrastructure for managing and maintaining App Service Environments via TLS.  Do not block traffic to this port.  This port is always bound to the public VIP of an ASE.
 * 80:  Default port for inbound HTTP traffic to apps running in App Service Plans in an App Service Environment.  On an ILB-enabled ASE, this port is bound to the ILB address of the ASE.
-* 443: Default port for inbound SSL traffic to apps running in App Service Plans in an App Service Environment.  On an ILB-enabled ASE, this port is bound to the ILB address of the ASE.
+* 443: Default port for inbound TLS traffic to apps running in App Service Plans in an App Service Environment.  On an ILB-enabled ASE, this port is bound to the ILB address of the ASE.
 * 21:  Control channel for FTP.  This port can be safely blocked if FTP is not being used.  On an ILB-enabled ASE, this port can be bound to the ILB address for an ASE.
 * 990:  Control channel for FTPS.  This port can be safely blocked if FTPS is not being used.  On an ILB-enabled ASE, this port can be bound to the ILB address for an ASE.
 * 10001-10020: Data channels for FTP.  As with the control channel, these ports can be safely blocked if FTP is not being used.  On an ILB-enabled ASE, this port can be bound to the ASE's ILB address.
@@ -58,7 +58,7 @@ The following demonstrates creating a network security group:
 
 Once a network security group is created, one or more network security rules are added to it.  Since the set of rules may change over time, it is recommended to space out the numbering scheme used for rule priorities to make it easy to insert additional rules over time.
 
-The example below shows a rule that explicitly grants access to the management ports needed by the Azure infrastructure to manage and maintain an App Service Environment.  Note that all management traffic flows over SSL and is secured by client certificates, so even though the ports are opened they are inaccessible by any entity other than Azure management infrastructure.
+The example below shows a rule that explicitly grants access to the management ports needed by the Azure infrastructure to manage and maintain an App Service Environment.  Note that all management traffic flows over TLS and is secured by client certificates, so even though the ports are opened they are inaccessible by any entity other than Azure management infrastructure.
 
     Get-AzureNetworkSecurityGroup -Name "testNSGexample" | Set-AzureNetworkSecurityRule -Name "ALLOW AzureMngmt" -Type Inbound -Priority 100 -Action Allow -SourceAddressPrefix 'INTERNET'  -SourcePortRange '*' -DestinationAddressPrefix '*' -DestinationPortRange '454-455' -Protocol TCP