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

roygara · roygara · commit f26e0e2b88ec · 2019-10-28T14:34:27.000-07:00
diff --git a/articles/cognitive-services/Bing-News-Search/csharp.md b/articles/cognitive-services/Bing-News-Search/csharp.md
@@ -8,7 +8,7 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: bing-news-search
 ms.topic: quickstart
-ms.date: 6/18/2019
+ms.date: 10/28/2019
 ms.author: aahi
 ms.custom: seodec2018
 ---
@@ -101,25 +101,6 @@ Create a method named `BingNewsSearch` to perform the call to the API, and set t
     return searchResult;
     ```
 
-3. Create the search result object, and extract the Bing HTTP headers. Then return `searchResult`.
-
-    ```csharp
-    // Create the result object for return
-    var searchResult = new SearchResult()
-    {
-        jsonResult = json,
-        relevantHeaders = new Dictionary<String, String>()
-    };
-
-    // Extract Bing HTTP headers
-    foreach (String header in response.Headers)
-    {
-        if (header.StartsWith("BingAPIs-") || header.StartsWith("X-MSEdge-"))
-            searchResult.relevantHeaders[header] = response.Headers[header];
-    }
-    return searchResult;
-    ```
-
 ## Process the response
 
 1. In the main method, call `BingNewsSearch()` and store the returned response. Then deserialize the JSON into an object. You can then view the values of the response.
diff --git a/articles/cosmos-db/sql-api-sdk-dotnet-changefeed.md b/articles/cosmos-db/sql-api-sdk-dotnet-changefeed.md
@@ -38,6 +38,15 @@ ms.author: maquaran
 
 ### v2 builds
 
+### <a name="2.2.8"/>2.2.8
+* Stability and diagnosability improvements:
+  * Added support to detect reading change feed taking long time. When it takes longer than the value specified by the `ChangeFeedProcessorOptions.ChangeFeedTimeout` property, the following steps are taken:
+    * The operation to read change feed on the problematic partition is aborted.
+    * The change feed processor instance drops ownership of the problematic lease. The dropped lease will be picked up during the next lease acquire step that will be done by the same or different change feed processor instance. This way, reading change feed will start over.
+    * An issue is reported to the health monitor. The default heath monitor sends all reported issues to trace log.
+  * Added a new public property: `ChangeFeedProcessorOptions.ChangeFeedTimeout`. The default value of this property is 10 mins.
+  * Added a new public enum value: `Monitoring.MonitoredOperation.ReadChangeFeed`. When the value of `HealthMonitoringRecord.Operation` is set to `Monitoring.MonitoredOperation.ReadChangeFeed`, it indicates the health issue is related to reading change feed.
+
 ### <a name="2.2.7"/>2.2.7
 * Improved load balancing strategy for scenario when getting all leases takes longer than lease expiration interval, e.g. due to network issues:
   * In this scenario load balancing algorithm used to falsely consider leases as expired, causing stealing leases from active owners. This could trigger unnecessary re-balancing a lot of leases.
@@ -165,6 +174,7 @@ Any request to Cosmos DB using a retired SDK will be rejected by the service.
 
 | Version | Release Date | Retirement Date |
 | --- | --- | --- |
+| [2.2.8](#2.2.8) |October 28, 2019 |--- |
 | [2.2.7](#2.2.7) |May 14, 2019 |--- |
 | [2.2.6](#2.2.6) |January 29, 2019 |--- |
 | [2.2.5](#2.2.5) |December 13, 2018 |--- |
diff --git a/articles/firewall/tutorial-firewall-deploy-portal.md b/articles/firewall/tutorial-firewall-deploy-portal.md
@@ -5,7 +5,7 @@ services: firewall
 author: vhorne
 ms.service: firewall
 ms.topic: tutorial
-ms.date: 08/29/2019
+ms.date: 10/28/2019
 ms.author: victorh
 ms.custom: mvc
 #Customer intent: As an administrator new to this service, I want to control outbound network access from resources located in an Azure subnet.
@@ -210,8 +210,10 @@ This is the network rule that allows outbound access to two IP addresses at port
 7. For **Protocol**, select **UDP**.
 8. For **Source Addresses**, type **10.0.2.0/24**.
 9. For Destination address, type **209.244.0.3,209.244.0.4**
-10. For **Destination Ports**, type **53**.
-11. Select **Add**.
+
+   These are public DNS servers operated by CenturyLink.
+1. For **Destination Ports**, type **53**.
+2. Select **Add**.
 
 ### Change the primary and secondary DNS address for the **Srv-Work** network interface
 
diff --git a/articles/frontdoor/waf-overview.md b/articles/frontdoor/waf-overview.md
@@ -102,14 +102,17 @@ Custom rules are always applied before rules in the Default Rule Set are evaluat
 
 ### Bot protection rule (preview)
 
-A managed Bot protection rule set can be enabled for your WAF to take custom actions on requests from known malicious IP addresses. The IP addresses are sourced from the Microsoft Threat Intelligence feed. [Intelligent Security Graph](https://www.microsoft.com/security/operations/intelligence) powers Microsoft threat intelligence and is used by multiple services including Azure Security Center.
+A managed Bot protection rule set can be enabled for your WAF to take custom actions on requests from known bot categories.
+There are 3 bot categories supported: bad bots, good bots and unknown bots. In the bad bots category, one rule detects malicious bots based on IP reputation of clieny addresses. IP reputation are sourced from the Microsoft Threat Intelligence feed. [Intelligent Security Graph](https://www.microsoft.com/security/operations/intelligence) powers Microsoft threat intelligence and is used by multiple services including Azure Security Center. In addition, requests that pretend to be known search engines are also detected as malicious.
+Good bots are validated seacrh engines. Unknown categories include requests are are identified as bots, but with unknown intentions. 
+You may set custom actions to Block, Allow, Log or redirect for different categories of Bots.
 
 ![Bot Protection Rule Set](./media/waf-front-door-configure-bot-protection/BotProtect2.png)
 
 > [!IMPORTANT]
 > Bot protection rule set is currently in public preview and is provided with a preview service level agreement. Certain features may not be supported or may have constrained capabilities.  See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for details.
 
-If Bot Protection is enabled, incoming requests that match Malicious Bots client IPs are logged at FrontdoorWebApplicationFirewallLog log. You may access WAF logs from storage account, event hub or log analytics. 
+If Bot Protection is enabled, incoming requests that match bot rules are logged at FrontdoorWebApplicationFirewallLog log. You may access WAF logs from storage account, event hub or log analytics. 
 
 ## Configuration
 
diff --git a/articles/iot-central/energy/tutorial-smart-meter-app.md b/articles/iot-central/energy/tutorial-smart-meter-app.md
@@ -91,7 +91,7 @@ Click on the **Device templates** tab to see the smart meter device model. The m
 ## Clean up resources
 If you decide to not continue using this application, delete your application with the following these steps:
 
-1. From the left-hand menu, open Administration tab
+1. From the left pane, open Administration tab
 2. Select Application settings and click Delete button at the bottom of the page. 
 
     > [!div class="mx-imgBorder"]
diff --git a/articles/iot-central/energy/tutorial-solar-panel-app.md b/articles/iot-central/energy/tutorial-solar-panel-app.md
@@ -93,7 +93,7 @@ Click on the **Device templates** tab to see the solar panel device model. The m
 ## Clean up resources
 If you decide to not continue using this application, delete your application with the following these steps:
 
-1. From the left-hand menu, open Administration tab
+1. From the left pane, open Administration tab
 2. Select Application settings and click Delete button at the bottom of the page. 
 
     [!div class="mx-imgBorder"]
diff --git a/articles/iot-central/government/tutorial-connected-waste-management.md b/articles/iot-central/government/tutorial-connected-waste-management.md
@@ -44,7 +44,7 @@ To create a new Azure IoT Central connected waste management application:
 
     ![Enter your organization account](./media/tutorial-connectedwastemanagement/sign-in.png)
 
-2. Click on **Build** from the left navigation menu and select the **Government** tab. The government page displays several government application templates.
+2. Click on **Build** from the left pane and select the **Government** tab. The government page displays several government application templates.
 
     ![Build Government App templates](./media/tutorial-connectedwastemanagement/iotcentral-government-tab-overview.png)
 
@@ -256,8 +256,8 @@ As a builder, you can change several settings to customize the user experience i
 
 If you're not going to continue to use this application, delete your application with the following steps:
 
-1. Open the Administration tab from the left navigation menu of your IoT Central application. 
-2. Select Application settings and click Delete button at the bottom of the page. 
+1. Open the Administration tab from the left pane of your IoT Central application.
+2. Select Application settings and click Delete button at the bottom of the page.
 
   
 
diff --git a/articles/iot-central/government/tutorial-water-consumption-monitoring.md b/articles/iot-central/government/tutorial-water-consumption-monitoring.md
@@ -44,7 +44,7 @@ To create a new Azure IoT Central water consumption monitoring application:
 
     ![Enter your organization account](media/tutorial-waterconsumptionmonitoring/sign-in.png)
 
-2. Click on **Build** from the left navigation menu and select the **Government** tab. The government page displays several government application templates.
+2. Click on **Build** from the left pane and select the **Government** tab. The government page displays several government application templates.
 
    ![Build Government App templates](./media/tutorial-waterconsumptionmonitoring/iotcentral-government-tab-overview1.png)
 
@@ -240,7 +240,7 @@ As a builder, you can change several settings to customize the user experience i
 
 If you're not going to continue to use this application, delete your application with the following steps:
 
-1. Open the Administration tab from the left navigation menu of your IoT Central application. 
+1. Open the Administration tab from the left pane of your IoT Central application. 
 2. Select Application settings and click Delete button at the bottom of the page. 
 
 
diff --git a/articles/iot-central/government/tutorial-water-quality-monitoring.md b/articles/iot-central/government/tutorial-water-quality-monitoring.md
@@ -48,7 +48,7 @@ To create a new Azure IoT Central water quality monitoring application:
 
     ![Enter your organization account](./media/tutorial-waterqualitymonitoring/sign-in.png)
 
-2. Click on **Build** from the left navigation menu and select the **Government** tab. The government page displays several government application templates.
+2. Click on **Build** from the left pane and select the **Government** tab. The government page displays several government application templates.
 
     ![Build Government App templates](./media/tutorial-waterqualitymonitoring/iotcentral-government-tab-overview1.png)
 
@@ -253,8 +253,8 @@ As a builder, you can change several settings to customize the user experience i
 
 If you're not going to continue to use this application, delete your application with the following steps:
 
-1. Open the Administration tab from the left navigation menu of your IoT Central application. 
-2. Select Application settings and click Delete button at the bottom of the page. 
+1. Open the Administration tab from the left pane of your IoT Central application.
+2. Select Application settings and click Delete button at the bottom of the page.
 
     ![Delete application](./media/tutorial-waterqualitymonitoring/waterqualitymonitoring-application-settings-delete-app1.png)        
 
diff --git a/articles/iot-edge/about-iot-edge.md b/articles/iot-edge/about-iot-edge.md
@@ -8,19 +8,20 @@ ms.reviewer: chipalost
 ms.service: iot-edge
 services: iot-edge
 ms.topic: overview
-ms.date: 04/17/2019
+ms.date: 10/28/2019
 ms.author: kgremban
 ms.custom: mvc
 ---
 
 # What is Azure IoT Edge
 
-Azure IoT Edge moves cloud analytics and custom business logic to devices so that your organization can focus on business insights instead of data management. Scale out your IoT solution by packaging your business logic into standard containers, then you can deploy those containers to any of your devices and monitor it all from the cloud. 
+Azure IoT Edge moves cloud analytics and custom business logic to devices so that your organization can focus on business insights instead of data management. Scale out your IoT solution by packaging your business logic into standard containers, then you can deploy those containers to any of your devices and monitor it all from the cloud.
 
-Analytics drives business value in IoT solutions, but not all analytics needs to be in the cloud. If you want to respond to emergencies as quickly as possible, you can run anomaly detection workloads at the edge. If you want to reduce bandwidth costs and avoid transferring terabytes of raw data, you can clean and aggregate the data locally then only send the insights to the cloud for analysis. 
+Analytics drives business value in IoT solutions, but not all analytics needs to be in the cloud. If you want to respond to emergencies as quickly as possible, you can run anomaly detection workloads at the edge. If you want to reduce bandwidth costs and avoid transferring terabytes of raw data, you can clean and aggregate the data locally then only send the insights to the cloud for analysis.
 
 Azure IoT Edge is made up of three components:
-* **IoT Edge modules** are containers that run Azure services, third-party services, or your own code. Modules are deployed to IoT Edge devices and execute locally on those devices. 
+
+* **IoT Edge modules** are containers that run Azure services, third-party services, or your own code. Modules are deployed to IoT Edge devices and execute locally on those devices.
 * The **IoT Edge runtime** runs on each IoT Edge device and manages the modules deployed to each device. 
 * A **cloud-based interface** enables you to remotely monitor and manage IoT Edge devices.
 
@@ -29,35 +30,35 @@ Azure IoT Edge is made up of three components:
 
 ## IoT Edge modules
 
-IoT Edge modules are units of execution, implemented as Docker compatible containers, that run your business logic at the edge. Multiple modules can be configured to communicate with each other, creating a pipeline of data processing. You can develop custom modules or package certain Azure services into modules that provide insights offline and at the edge. 
+IoT Edge modules are units of execution, implemented as Docker compatible containers, that run your business logic at the edge. Multiple modules can be configured to communicate with each other, creating a pipeline of data processing. You can develop custom modules or package certain Azure services into modules that provide insights offline and at the edge.
 
 ### Artificial intelligence at the edge
 
-Azure IoT Edge allows you to deploy complex event processing, machine learning, image recognition, and other high value AI without writing it in-house. Azure services like Azure Functions, Azure Stream Analytics, and Azure Machine Learning can all be run on-premises via Azure IoT Edge. You’re not limited to Azure services, though. Anyone is able to create AI modules and make them available to the community for use through the Azure Marketplace. 
+Azure IoT Edge allows you to deploy complex event processing, machine learning, image recognition, and other high value AI without writing it in-house. Azure services like Azure Functions, Azure Stream Analytics, and Azure Machine Learning can all be run on-premises via Azure IoT Edge. You’re not limited to Azure services, though. Anyone is able to create AI modules and make them available to the community for use through the Azure Marketplace.
 
 ### Bring your own code
 
-When you want to deploy your own code to your devices, Azure IoT Edge supports that, too. Azure IoT Edge holds to the same programming model as the other Azure IoT services. The same code can be run on a device or in the cloud. Azure IoT Edge supports both Linux and Windows so you can code to the platform of your choice. It supports Java, .NET Core 2.0, Node.js, C, and Python so your developers can code in a language they already know and use existing business logic.
+When you want to deploy your own code to your devices, Azure IoT Edge supports that, too. Azure IoT Edge holds to the same programming model as the other Azure IoT services. You can run the same code on a device or in the cloud. Azure IoT Edge supports both Linux and Windows so you can code to the platform of your choice. It supports Java, .NET Core 2.0, Node.js, C, and Python so your developers can code in a language they already know and use existing business logic.
 
 ## IoT Edge runtime
 
-The Azure IoT Edge runtime enables custom and cloud logic on IoT Edge devices. It sits on the IoT Edge device, and performs management and communication operations. The runtime performs several functions:
+The Azure IoT Edge runtime enables custom and cloud logic on IoT Edge devices. The runtime sits on the IoT Edge device, and performs management and communication operations. The runtime performs several functions:
 
-* Install and update workloads on the device.
-* Maintain Azure IoT Edge security standards on the device.
-* Ensure that IoT Edge modules are always running.
-* Report module health to the cloud for remote monitoring.
-* Manage communication between downstream leaf devices and an IoT Edge device, between modules on an IoT Edge device, and between an IoT Edge device and the cloud.
+* Installs and update workloads on the device.
+* Maintains Azure IoT Edge security standards on the device.
+* Ensures that IoT Edge modules are always running.
+* Reports module health to the cloud for remote monitoring.
+* Manages communication between downstream leaf devices and an IoT Edge device, between modules on an IoT Edge device, and between an IoT Edge device and the cloud.
 
 ![IoT Edge runtime sends insights and reporting to IoT Hub](./media/about-iot-edge/runtime.png)
 
-How you use an Azure IoT Edge device is up to you. The runtime is often used to deploy AI to gateway devices which aggregate and process data from other on-premises devices, but this deployment model is just one option. 
+How you use an Azure IoT Edge device is up to you. The runtime is often used to deploy AI to gateway devices which aggregate and process data from other on-premises devices, but this deployment model is just one option.
 
-The Azure IoT Edge runtime runs on a large set of IoT devices to enable using the runtime in a wide variety of ways. It supports both Linux and Windows operating systems and abstracts hardware details. Use a device smaller than a Raspberry Pi 3 if you’re not processing much data, or use an industrial server to run resource-intensive workloads.
+The Azure IoT Edge runtime runs on a large set of IoT devices that enables using it in a wide variety of ways. It supports both Linux and Windows operating systems and abstracts hardware details. Use a device smaller than a Raspberry Pi 3 if you’re not processing much data, or use an industrial server to run resource-intensive workloads.
 
 ## IoT Edge cloud interface
 
-It's difficult to manage the software lifecycle for millions of IoT devices that are often different makes and models or geographically scattered. Workloads are created and configured for a particular type of device, deployed to all of your devices, and monitored to catch any misbehaving devices. These activities can’t be done on a per device basis and must be done at scale.
+It's difficult to manage the software life cycle for millions of IoT devices that are often different makes and models or geographically scattered. Workloads are created and configured for a particular type of device, deployed to all of your devices, and monitored to catch any misbehaving devices. These activities can’t be done on a per device basis and must be done at scale.
 
 Azure IoT Edge integrates seamlessly with Azure IoT solution accelerators to provide one control plane for your solution’s needs. Cloud services allow you to:
 
@@ -69,4 +70,4 @@ Azure IoT Edge integrates seamlessly with Azure IoT solution accelerators to pro
 
 ## Next steps
 
-Try out these concepts by [deploying IoT Edge on a simulated device](quickstart.md).
+Try out these concepts by [deploying IoT Edge on a simulated device](quickstart.md).
diff --git a/articles/load-balancer/load-balancer-ipv6-internet-cli.md b/articles/load-balancer/load-balancer-ipv6-internet-cli.md
diff --git a/articles/load-balancer/load-balancer-ipv6-internet-ps.md b/articles/load-balancer/load-balancer-ipv6-internet-ps.md
diff --git a/articles/load-balancer/load-balancer-ipv6-internet-template.md b/articles/load-balancer/load-balancer-ipv6-internet-template.md
