Merge pull request #93755 from MicrosoftDocs/master

10/28 AM Publish

Author: huypub

.openpublishing.redirection.json

@@ -43,7 +43,7 @@ Classic virtual networks aren't supported for new deployments. Existing managed
 Yes. Azure AD Domain Services can be enabled in an Azure Resource Manager virtual network. Classic Azure virtual networks are no longer supported for when you create a new managed domain.
 
 ### Can I migrate my existing managed domain from a Classic virtual network to a Resource Manager virtual network?
-Yes, this feature is in preview. For more information, see [Migrate Azure AD Domain Services from the Classic virtual network model to Resource Manager (preview)][migrate-from-classic-vnet.md]
+Yes, this feature is in preview. For more information, see [Migrate Azure AD Domain Services from the Classic virtual network model to Resource Manager (preview)](migrate-from-classic-vnet.md).
 
 ### Can I enable Azure AD Domain Services in an Azure CSP (Cloud Solution Provider) subscription?
 Yes. For more information, see [how to enable Azure AD Domain Services in Azure CSP subscriptions](csp.md).

articles/active-directory-domain-services/faqs.md

@@ -88,6 +88,10 @@ Azure Dev Spaces is currently only available for Linux-based node pools.
 
 Group managed service accounts (gMSA) support is not currently available in AKS.
 
+## Can I use Azure Monitor for containers with Windows nodes and containers?
+
+Yes you can, however Azure Monitor does not gather logs (stdout) from Windows containers. You can still attach to the live stream of stdout logs from a Windows container.
+
 ## What if I need a feature which is not supported?
 
 We work hard to bring all the features you need to Windows in AKS, but if you do encounter gaps, the open-source, upstream [aks-engine][aks-engine] project provides an easy and fully customizable way of running Kubernetes in Azure, including Windows support. Please make sure to check out our roadmap of features coming [AKS roadmap][aks-roadmap].

articles/aks/windows-node-limitations.md

@@ -150,7 +150,7 @@ Starting with Ansible 2.8, Ansible provides an [Azure dynamic-inventory plug-in]
     Failed to connect to the host via ssh: Host key verification failed.
     ```
     
-    If you do receive the "host-key verification" error, add the following line to the Ansible configuration file. The Ansible configuration file is located at `/etc/ansible/ansible.cfg`.
+    If you do receive the "host-key verification" error, add the following line to the Ansible configuration file. The Ansible configuration file is located at `/etc/ansible/ansible.cfg` or `~/.ansible.cfg`.
 
     ```bash
     host_key_checking = False

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

@@ -23,7 +23,7 @@ experiment_id: 1e304dc9-5add-4b
 
 In this quickstart, you deploy a Python web app to [App Service on Linux](app-service-linux-intro.md), Azure's highly scalable, self-patching web hosting service. You use the local [Azure command-line interface (CLI)](/cli/azure/install-azure-cli) on a Mac, Linux, or Windows computer. The web app you configure uses a free App Service tier, so you incur no costs in the course of this article.
 
-If you prefer to deploy apps through an IDE, see [Deploy Python apps to App Service from Visual Studio Code](/python/tutorial-deploy-app-service-on-linux-01).
+If you prefer to deploy apps through an IDE, see [Deploy Python apps to App Service from Visual Studio Code](/azure/python/tutorial-deploy-app-service-on-linux-01).
 
 ## Prerequisites
 
@@ -172,7 +172,7 @@ Once deployment has completed, switch back to the browser window open to `http:/
 ![Run an updated sample Python app in Azure](./media/quickstart-python/run-updated-hello-world-sample-python-app-in-browser.png)
 
 > [!TIP]
-> Visual Studio Code provides powerful extensions for Python and Azure App Service, which simplify the process of deploying Python web apps to App Service. For more information, see [Deploy Python apps to App Service from Visual Studio Code](/python/tutorial-deploy-app-service-on-linux-01).
+> Visual Studio Code provides powerful extensions for Python and Azure App Service, which simplify the process of deploying Python web apps to App Service. For more information, see [Deploy Python apps to App Service from Visual Studio Code](/azure/python/tutorial-deploy-app-service-on-linux-01).
 
 ## Stream logs
 

articles/app-service/containers/quickstart-python.md

@@ -165,9 +165,9 @@ If you encounter an issue, container logs are the best way to learn about the st
 
    | Name | IMAGE |
    | --- | --- |
-   | azureiotsecurity | mcr.microsoft.com/ascforiot/azureiotsecurity:1.0.0 |
+   | azureiotsecurity | mcr.microsoft.com/ascforiot/azureiotsecurity:1.0.1 |
    | edgeHub | mcr.microsoft.com/azureiotedge-hub:1.0.8.3 |
-   | edgeAgent | mcr.microsoft.com/azureiotedge-agent:1.0 |
+   | edgeAgent | mcr.microsoft.com/azureiotedge-agent:1.0.1 |
 
    If the minimum required containers are not present, check if your IoT Edge deployment manifest is aligned with the recommended settings. For more information, see [Deploy IoT Edge module](#deployment-using-azure-portal).
 

articles/asc-for-iot/how-to-deploy-edge.md

@@ -42,7 +42,7 @@ To enable security on your IoT Hub:
 
 1. Open your **IoT Hub** in Azure portal. 
 1. Under the **Security** menu, click **Secure your IoT solution**.    
-1. Click **Save**. 
+
 
 Congratulations! You've completed enabling Azure Security Center for IoT on your IoT Hub. 
 

articles/asc-for-iot/quickstart-onboard-iot-hub.md

@@ -248,7 +248,6 @@ The following examples show trigger binding in a *function.json* file and [Java
     ) 
     String content, 
     final ExecutionContext context) {
-      // log 
       context.getLogger().info("Event content: " + content);      
   }
 ```
@@ -285,7 +284,6 @@ Upon arrival, the event's JSON payload is de-serialized into the ```EventSchema`
     ) 
     EventSchema event, 
     final ExecutionContext context) {
-      // log 
       context.getLogger().info("Event content: ");
       context.getLogger().info("Subject: " + event.subject);
       context.getLogger().info("Time: " + event.eventTime); // automatically converted to Date by the runtime

articles/azure-functions/functions-bindings-event-grid.md

@@ -250,8 +250,8 @@ The following table explains the binding configuration properties that you set i
 
 |function.json property | Attribute property |Description|
 |---------|---------|----------------------|
-|**type** |n/a| Must be set to "notificationHub". |
-|**direction** |n/a| Must be set to "out". | 
+|**type** |n/a| Must be set to `notificationHub`. |
+|**direction** |n/a| Must be set to `out`. | 
 |**name** |n/a| Variable name used in function code for the notification hub message. |
 |**tagExpression** |**TagExpression** | Tag expressions allow you to specify that notifications be delivered to a set of devices that have registered to receive notifications that match the tag expression.  For more information, see [Routing and tag expressions](../notification-hubs/notification-hubs-tags-segment-push-message.md). |
 |**hubName** | **HubName** | Name of the notification hub resource in the Azure portal. |

articles/azure-functions/functions-bindings-notification-hubs.md

@@ -58,7 +58,7 @@ logs a Service Bus queue message:
 ```cs
 [FunctionName("ServiceBusQueueTriggerCSharp")]                    
 public static void Run(
-    [ServiceBusTrigger("myqueue", AccessRights.Manage, Connection = "ServiceBusConnection")] 
+    [ServiceBusTrigger("myqueue", Connection = "ServiceBusConnection")] 
     string myQueueItem,
     Int32 deliveryCount,
     DateTime enqueuedTimeUtc,
@@ -72,12 +72,6 @@ public static void Run(
 }
 ```
 
-This example is for Azure Functions version 1.x. To make this code work for 2.x:
-
-- [omit the access rights parameter](#trigger---configuration)
-- change the type of the log parameter from `TraceWriter` to `ILogger`
-- change `log.Info` to `log.LogInformation`
-
 ### Trigger - C# script example
 
 The following example shows a Service Bus trigger binding in a *function.json* file and a [C# script function](functions-reference-csharp.md) that uses the binding. The function reads [message metadata](#trigger---message-metadata) and logs a Service Bus queue message.