Merge pull request #111143 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/Microsoft/azure-docs (branch master)

Author: tfosmark

articles/app-service/webjobs-dotnet-deploy-vs.md

@@ -221,7 +221,7 @@ WebJobs uses the same CRON expressions for scheduling as the timer trigger in Az
 
 [!INCLUDE [webjobs-cron-timezone-note](../../includes/webjobs-cron-timezone-note.md)]
 
-### setting.job reference
+### settings.job reference
 
 The following settings are supported by WebJobs:
 

articles/automation/troubleshoot/desired-state-configuration.md

@@ -109,6 +109,8 @@ VM has reported a failure when processing extension 'Microsoft.Powershell.DSC /
 
 This issue is caused by a bad or expired certificate.  For more information, see [Certificate expiration and reregistration](../automation-dsc-onboarding.md#re-registering-a-node).
 
+This issue could also be caused by a proxy configuration not allowing access to ***.azure-automation.net**. For more information, see [Configuration of private networks](../automation-dsc-overview.md#network-planning). 
+
 ### Resolution
 
 Follow the steps listed below to re-register the failing DSC node.

articles/azure-government/documentation-government-compute.md

@@ -24,6 +24,17 @@ For details on this service and how to use it, see [Azure Virtual Machines Sizes
 ### Variations
 For available virtual machine sizes in Azure Government, see <a href="https://azure.microsoft.com/regions/services/">Products Available by Region</a>
 
+The following Virtual Machines features are not currently available in Azure Government:
+
+- Settings
+  - Continuous delivery
+- Operations
+  - Auto-Shutdown
+- Monitoring
+  - Application Insights
+- Support + Troubleshooting
+  - Ubuntu Advantage support plan
+
 ### Data Considerations
 The following information identifies the Azure Government boundary for Azure Virtual Machines:
 
@@ -63,7 +74,6 @@ The [Azure Functions](https://docs.microsoft.com/azure/azure-functions/) service
 ### Variations
 The following Functions features are not currently available in Azure Government:
 
-- The [App Service plan](../azure-functions/functions-scale.md#app-service-plan) is available in Azure Government. The Consumption plan is available in USGov Virginia region. To learn more about the two hosting plans, click [here](../azure-functions/functions-scale.md)
 - [Monitoring via Application Insights](../azure-functions/functions-monitoring.md) is not available yet.
 
 The URLs for Function are different:

articles/azure-government/documentation-government-services-aiandcognitiveservices.md

@@ -51,7 +51,7 @@ Variations in Azure Government:
 
 - Custom Vision Portal: https://www.customvision.azure.us
 - Endpoint URL: https://virginia.api.cognitive.microsoft.us/customvision/v3.0/
-- Available SKUs: F0,S0
+- Available SKUs: S0
 
 For more information, see the [global Azure documentation](https://go.microsoft.com/fwlink/?linkid=848046), [Custom Vision Training API reference](https://go.microsoft.com/fwlink/?linkid=865445), and [Custom Vision Prediction API reference](https://go.microsoft.com/fwlink/?linkid=865446)
 
@@ -128,7 +128,7 @@ Variations in Azure Government:
 - Endpoint: https://virginia.api.cognitive.microsoft.us/luis/v2.0
 - LUIS portal: https://luis.azure.us
 - Available SKUs: S0
-- Speech Requests, Speech Priming, Spell Check, and Prebuilt Domains are not currently available
+- Speech Requests and Prebuilt Domains are not currently available
 
 For more information, see [global Azure documentation](../cognitive-services/luis/what-is-luis.md) for Language Understanding.
 

articles/azure-monitor/app/ilogger.md

@@ -209,7 +209,7 @@ You can still use the old provider. (It will be removed only in a major version
 - In ASP.NET Core (2.0 and later), the recommended way to  [enable logging providers](https://github.com/aspnet/Announcements/issues/255) is by using extension methods on ILoggingBuilder in **Program.cs** itself.
 
 > [!Note]
-> The new provider is available for applications that target NETSTANDARD2.0 or later. If your application targets older .NET Core versions, such as .NET Core 1.1, or if it targets the .NET Framework, continue to use the old provider.
+> The new provider is available for applications that target NETSTANDARD2.0 or later. From [Microsoft.ApplicationInsights.AspNet SDK](https://www.nuget.org/packages/Microsoft.ApplicationInsights.AspNetCore) version 2.14.0 onwards, new provider is also available for applications that target .NET Framework NET461 or later. If your application targets older .NET Core versions, such as .NET Core 1.1, or if it targets the .NET Framework less than NET46, continue to use the old provider.
 
 ## Console application
 

articles/virtual-network/tutorial-create-route-table-portal.md

@@ -203,7 +203,7 @@ Before you select **Create** to create the public or private VM, go to the follo
 | Basics | Resource group | **myResourceGroup** |
 | | Virtual machine name | *myVmPublic* |
 | | Public inbound ports | **Allow selected ports** |
-| | Select inbound ports | **HTTP** and **RDP** |
+| | Select inbound ports | **RDP** |
 | Networking | Virtual network | **myVirtualNetwork** |
 | | Subnet | **Public (10.0.0.0/24)** |
 | | Public IP address | The default |
@@ -216,7 +216,7 @@ Before you select **Create** to create the public or private VM, go to the follo
 | Basics | Resource group | **myResourceGroup** |
 | | Virtual machine name | *myVmPrivate* |
 | | Public inbound ports | **Allow selected ports** |
-| | Select inbound ports | **HTTP** and **RDP** |
+| | Select inbound ports | **RDP** |
 | Networking | Virtual network | **myVirtualNetwork** |
 | | Subnet | **Private (10.0.1.0/24)** |
 | | Public IP address | The default |