Merge pull request #50680 from MicrosoftDocs/master

8/31 PM Publish

Author: huypub

.openpublishing.redirection.json

@@ -26094,7 +26094,12 @@
         },
         {
             "source_path": "articles/iot-suite/iot-suite-time-series-insights.md",
-            "redirect_url": "/azure/iot-accelerators/iot-accelerators-time-series-insights",
+            "redirect_url": "/azure/iot-accelerators/iot-accelerators-remote-monitoring-time-series-insights",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/iot-suite/iot-accelerators-time-series-insights.md",
+            "redirect_url": "/azure/iot-accelerators/iot-accelerators-remote-monitoring-time-series-insights",
             "redirect_document_id": false
         },
         {

articles/active-directory/connect/active-directory-aadconnect-azure-adfs.md

@@ -182,18 +182,21 @@ Select the newly created ILB in the Load Balancers panel. It will open the setti
 
 **6.3. Configuring probe**
 
-In the ILB settings panel, select Probes.
+In the ILB settings panel, select Health probes.
 
 1. Click on add
 2. Provide details for probe
    a. **Name**: Probe name
-   b. **Protocol**: TCP
-   c. **Port**: 443 (HTTPS)
-   d. **Interval**: 5 (default value) – this is the interval at which ILB will probe the machines in the backend pool
-   e. **Unhealthy threshold limit**: 2 (default value) – this is the threshold of consecutive probe failures after which ILB will declare a machine in the backend pool non-responsive and stop sending traffic to it.
+   b. **Protocol**: HTTP
+   c. **Port**: 80 (HTTP)
+   d. **Path**: /adfs/probe 
+   e. **Interval**: 5 (default value) – this is the interval at which ILB will probe the machines in the backend pool
+   f. **Unhealthy threshold limit**: 2 (default value) – this is the threshold of consecutive probe failures after which ILB will declare a machine in the backend pool non-responsive and stop sending traffic to it.
 
 ![Configure ILB probe](./media/active-directory-aadconnect-azure-adfs/ilbdeployment4.png)
 
+We are using the /adfs/probe endpoint that was created explictly for health checks in an AD FS environment where a full HTTPS path check cannot happen.  This is substantially better than a basic port 443 check, which does not accurately reflect the status of a modern AD FS deployment.  More information on this can be found at https://blogs.technet.microsoft.com/applicationproxyblog/2014/10/17/hardware-load-balancer-health-checks-and-web-application-proxy-ad-fs-2012-r2/.
+
 **6.4. Create load balancing rules**
 
 In order to effectively balance the traffic, the ILB should be configured with load balancing rules. In order to create a load balancing rule, 

articles/active-directory/reports-monitoring/tutorial-access-api-with-certificates.md

@@ -34,7 +34,7 @@ This involves the following steps:
 
 1. First, make sure that you have completed the [prerequisites to access the Azure Active Directory reporting API](howto-configure-prerequisites-for-reporting-api.md). 
 
-2. Download and install Azure AD Powershell V2, following the instructions at [Azure Active Directory PowerShell](https://github.com/Azure/azure-docs-powershell-azuread/blob/master/Azure AD Cmdlets/AzureAD/index.md)
+2. Download and install Azure AD Powershell V2, following the instructions at [Azure Active Directory PowerShell(https://github.com/Azure/azure-docs-powershell-azuread/blob/master/docs-conceptual/azureadps-2.0/install-adv2.md)
 
 3. Install the MSCloudIDUtils from the [PowerShellGallery - MSCloudIdUtils](https://www.powershellgallery.com/packages/MSCloudIdUtils/). This module provides several utility cmdlets including:
     - The ADAL libraries needed for authentication

articles/active-directory/saas-apps/pingboard-provisioning-tutorial.md

@@ -23,7 +23,7 @@ ms.reviewer: asmalser
 
 # Tutorial: Configure Pingboard for automatic user provisioning
 
-The objective of this tutorial is to show you the steps you need to perform to enable automatic provisioning and de-provisioning of user accounts from Azure Active Directory (Azure AD) to Pingboard.
+The purpose of this tutorial is to show you the steps you need to follow to enable automatic provisioning and de-provisioning of user accounts from Azure Active Directory (Azure AD) to Pingboard.
 
 ## Prerequisites
 
@@ -34,7 +34,7 @@ The scenario outlined in this tutorial assumes that you already have the followi
 *   A user account in Pingboard with admin permissions 
 
 > [!NOTE] 
-> Azure AD provisioning integration relies on the [Pingboard API](`https://your_domain.pingboard.com/scim/v2`), which is available to your account.
+> Azure AD provisioning integration relies on the [Pingboard API](https://pingboard.docs.apiary.io/#), which is available to your account.
 
 ## Assign users to Pingboard
 
@@ -50,7 +50,7 @@ We recommend that you assign a single Azure AD user to Pingboard to test the pro
 
 ## Configure user provisioning to Pingboard 
 
-This section guides you through connecting your Azure AD to the Pingboard user account provisioning API. You also configure the provisioning service to create, update, and disable assigned user accounts in Pingboard based on user assignments in Azure AD.
+This section guides you through connecting your Azure AD to the Pingboard user account provisioning API. You also configure the provisioning service to create, update, and disable assigned user accounts in Pingboard that are based on user assignments in Azure AD.
 
 > [!TIP]
 > To enable SAML-based single sign-on for Pingboard, follow the instructions provided in the [Azure portal](https://portal.azure.com). Single sign-on can be configured independently of automatic provisioning, although these two features complement each other.
@@ -67,7 +67,7 @@ This section guides you through connecting your Azure AD to the Pingboard user a
 
     ![Pingboard Provisioning](./media/pingboard-provisioning-tutorial/pingboardazureprovisioning.png)
 
-1. Under the **Admin Credentials** section, perform the following steps:
+1. Under the **Admin Credentials** section, use the following steps:
 
     a. In **Tenant URL**, enter `https://your_domain.pingboard.com/scim/v2`, and replace "your_domain" with your real domain.
 
@@ -79,7 +79,7 @@ This section guides you through connecting your Azure AD to the Pingboard user a
 
     e. Copy the token in **OAuth Bearer Token**, and enter it in **Secret Token**.
 
-1. In the Azure portal, select **Test Connection** to ensure Azure AD can connect to your Pingboard app. If the connection fails, ensure that your Pingboard account has admin permissions, and try the **Test Connection** step again.
+1. In the Azure portal, select **Test Connection** to test Azure AD can connect to your Pingboard app. If the connection fails, test that your Pingboard account has admin permissions, and try the **Test Connection** step again.
 
 1. Enter the email address of a person or group that you want to receive provisioning error notifications in **Notification Email**. Select the check box underneath.
 
@@ -93,7 +93,7 @@ This section guides you through connecting your Azure AD to the Pingboard user a
 
 1. Select **Save** to start the initial synchronization of users assigned to Pingboard.
 
-The initial synchronization takes longer to perform than subsequent syncs, which occur approximately every 40 minutes as long as the service is running. Use the **Synchronization Details** section to monitor progress and follow links to provisioning activity logs. The logs describe all actions performed by the provisioning service on your Pingboard app.
+The initial synchronization takes longer to run than following syncs, which occur approximately every 40 minutes as long as the service is running. Use the **Synchronization Details** section to monitor progress and follow links to provisioning activity logs. The logs describe all actions taken by the provisioning service on your Pingboard app.
 
 For more information on how to read the Azure AD provisioning logs, see [Report on automatic user account provisioning](../active-directory-saas-provisioning-reporting.md).
 

articles/ansible/ansible-manage-azure-dynamic-inventories.md

@@ -131,20 +131,21 @@ The purpose of tags is to enable the ability to quickly and easily work with sub
 
 1. Insert the following code into the newly created `nginx.yml` file:
 
-    ```yml
-    - name: Install and start Nginx on an Azure virtual machine
-    hosts: azure
-    become: yes
-    tasks:
-    - name: install nginx
-        apt: pkg=nginx state=installed
-        notify:
-        - start nginx
-
-    handlers:
-    - name: start nginx
-        service: name=nginx state=started
-    ```
+```yml
+---
+- name: Install and start Nginx on an Azure virtual machine
+  hosts: azure
+  become: yes
+  tasks:
+  - name: install nginx
+    apt: pkg=nginx state=installed
+    notify:
+    - start nginx
+
+  handlers:
+  - name: start nginx
+    service: name=nginx state=started
+```
 
 1. Run the `nginx.yml` playbook:
 

articles/app-service/app-service-security.md

@@ -25,7 +25,7 @@ The platform components of App Service, including Azure VMs, storage, network co
 
 - Your app resources are [secured](https://github.com/projectkudu/kudu/wiki/Azure-Web-App-sandbox) from the other customers' Azure resources.
 - [VM instances and runtime software are regularly updated](app-service-patch-os-runtime.md) to address newly discovered vulnerabilities. 
-- Communication of secrets (such as connection strings) between your app and other Azure resources (such as [SQL Database](/services/sql-database/)) stays within Azure and doesn't cross any network boundaries. Secrets are always encrypted when stored.
+- Communication of secrets (such as connection strings) between your app and other Azure resources (such as [SQL Database](https://azure.microsoft.com/services/sql-database/)) stays within Azure and doesn't cross any network boundaries. Secrets are always encrypted when stored.
 - All communication over the App Service connectivity features, such as [hybrid connection](app-service-hybrid-connections.md), is encrypted. 
 - Connections with remote management tools like Azure PowerShell, Azure CLI, Azure SDKs, REST APIs, are all encrypted.
 - 24-hour threat management protects the infrastructure and platform against malware, distributed denial-of-service (DDoS), man-in-the-middle (MITM), and other threats.
@@ -80,7 +80,7 @@ In each of these cases, App Service provides a way for you to make secure connec
 
 ### Azure resources
 
-When your app connects to Azure resources, such as [SQL Database](/services/sql-database/) and [Azure Storage](/azure/storage/), the connection stays within Azure and doesn't cross any network boundaries. However, the connection goes through the shared networking in Azure, so always make sure that your connection is encrypted. 
+When your app connects to Azure resources, such as [SQL Database](https://azure.microsoft.com/services/sql-database/) and [Azure Storage](/azure/storage/), the connection stays within Azure and doesn't cross any network boundaries. However, the connection goes through the shared networking in Azure, so always make sure that your connection is encrypted. 
 
 If your app is hosted in an [App Service environment](environment/intro.md), you should [connect to supported Azure services using Virtual Network service endpoints](../virtual-network/virtual-network-service-endpoints-overview.md).
 
@@ -113,4 +113,4 @@ Except for the **Isolated** pricing tier, all tiers run your apps on the shared
 - Serve internal application using an internal load balancer (ILB), which allows access only from inside your Azure Virtual Network. The ILB has an IP address from your private subnet, which provides total isolation of your apps from the internet.
 - [Use an ILB behind a web application firewall (WAF)](environment/integrate-with-application-gateway.md). The WAF offers enterprise-level protection to your public-facing applications, such as DDoS protection, URI filtering, and SQL injection prevention.
 
-For more information, see [Introduction to Azure App Service Environments](environment/intro.md).
+For more information, see [Introduction to Azure App Service Environments](environment/intro.md). 

articles/app-service/web-sites-scale.md

@@ -108,7 +108,7 @@ For a table of service limits, quotas, and constraints, and supported features i
   * [How Azure Websites Scale - with Stefan Schackow](https://azure.microsoft.com/resources/videos/how-azure-web-sites-scale/)
 
 <!-- LINKS -->
-[vmsizes]:/pricing/details/app-service/
+[vmsizes]:https://azure.microsoft.com/pricing/details/app-service/
 [SQLaccountsbilling]:http://go.microsoft.com/fwlink/?LinkId=234930
 [azuresubscriptions]:https://account.windowsazure.com/subscriptions
 [portal]: https://portal.azure.com/

articles/automation/automation-schedules.md

@@ -27,7 +27,7 @@ The cmdlets in the following table are used to create and manage schedules with
 | [New-AzureRmAutomationSchedule](/powershell/module/azurerm.automation/new-azurermautomationschedule) |Creates a new schedule. |
 | [Remove-AzureRmAutomationSchedule](/powershell/module/azurerm.automation/remove-azurermautomationschedule) |Removes a schedule. |
 | [Set-AzureRmAutomationSchedule](/powershell/module/azurerm.automation/set-azurermautomationschedule) |Sets the properties for an existing schedule. |
-| [Get-AzureRmAutomationScheduledRunbook](/powershell/module/azurerm.automation/set-azurermautomationscheduledrunbook) |Retrieves scheduled runbooks. |
+| [Get-AzureRmAutomationScheduledRunbook](/powershell/module/azurerm.automation/get-azurermautomationscheduledrunbook) |Retrieves scheduled runbooks. |
 | [Register-AzureRmAutomationScheduledRunbook](/powershell/module/azurerm.automation/register-azurermautomationscheduledrunbook) |Associates a runbook with a schedule. |
 | [Unregister-AzureRmAutomationScheduledRunbook](/powershell/module/azurerm.automation/unregister-azurermautomationscheduledrunbook) |Dissociates a runbook from a schedule. |
 
@@ -120,4 +120,4 @@ Set-AzureRmAutomationSchedule –AutomationAccountName $automationAccountName `
 
 ## Next steps
 
-* To get started with runbooks in Azure Automation, see [Starting a Runbook in Azure Automation](automation-starting-a-runbook.md)
+* To get started with runbooks in Azure Automation, see [Starting a Runbook in Azure Automation](automation-starting-a-runbook.md)

articles/automation/automation-update-management.md

@@ -113,7 +113,7 @@ If your System Center Operations Manager management group is connected to a Log
 For more information about how solution management packs are updated, see [Connect Operations Manager to Log Analytics](../log-analytics/log-analytics-om-agents.md).
 
 > [!NOTE]
-> For systems with the Operations Manger Agent, to be able to be fully managed by Update Management, the agent needs to be updated to the Microsoft Monitoring Agent. To learn how to update the agent, see [How to upgrade an Operations Manager agent](/system-center/scom/deploy-upgrade-agents.md).
+> For systems with the Operations Manger Agent, to be able to be fully managed by Update Management, the agent needs to be updated to the Microsoft Monitoring Agent. To learn how to update the agent, see [How to upgrade an Operations Manager agent](/system-center/scom/deploy-upgrade-agents).
 
 ### Confirm that non-Azure machines are onboarded