Merge pull request #84074 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: huypub

articles/active-directory/users-groups-roles/licensing-service-plan-reference.md

@@ -101,6 +101,7 @@ When managing licenses in [the Azure portal](https://portal.azure.com/#blade/Mic
 | SKYPE FOR BUSINESS PSTN CONFERENCING	| MCOMEETADV	| 0c266dff-15dd-4b49-8397-2bb16070ed52	| MCOMEETADV (3e26ee1f-8a5f-4d52-aee2-b81ce45c8f40) | AUDIO CONFERENCING (3e26ee1f-8a5f-4d52-aee2-b81ce45c8f40) |
 | SKYPE FOR BUSINESS PSTN DOMESTIC AND INTERNATIONAL CALLING	| MCOPSTN2	| d3b4fe1f-9992-4930-8acb-ca6ec609365e	| MCOPSTN2 (5a10155d-f5c1-411a-a8ec-e99aae125390) | DOMESTIC AND INTERNATIONAL CALLING PLAN (5a10155d-f5c1-411a-a8ec-e99aae125390) |
 | SKYPE FOR BUSINESS PSTN DOMESTIC CALLING	| MCOPSTN1	| 0dab259f-bf13-4952-b7f8-7db8f131b28d	| MCOPSTN1 (4ed3ff63-69d7-4fb7-b984-5aec7f605ca8) | DOMESTIC CALLING PLAN (4ed3ff63-69d7-4fb7-b984-5aec7f605ca8) |
+| SKYPE FOR BUSINESS PSTN DOMESTIC CALLING	(120 Minutes)| MCOPSTN5	| 54a152dc-90de-4996-93d2-bc47e670fc06	| MCOPSTN5 (54a152dc-90de-4996-93d2-bc47e670fc06) | DOMESTIC CALLING PLAN (54a152dc-90de-4996-93d2-bc47e670fc06) |
 | VISIO ONLINE PLAN 1	| VISIOONLINE_PLAN1	| 4b244418-9658-4451-a2b8-b5e2b364e9bd	| ONEDRIVE_BASIC (da792a53-cbc0-4184-a10d-e544dd34b3c1)<br/>VISIOONLINE (2bdbaf8f-738f-4ac7-9234-3c3ee2ce7d0f) | ONEDRIVE_BASIC (da792a53-cbc0-4184-a10d-e544dd34b3c1)<br/>VISIOONLINE (2bdbaf8f-738f-4ac7-9234-3c3ee2ce7d0f) |
 | VISIO Online Plan 2	| VISIOCLIENT	| c5928f49-12ba-48f7-ada3-0d743a3601d5	| ONEDRIVE_BASIC (da792a53-cbc0-4184-a10d-e544dd34b3c1)<br/>VISIO_CLIENT_SUBSCRIPTION (663a804f-1c30-4ff0-9915-9db84f0d1cea)<br/>VISIOONLINE (2bdbaf8f-738f-4ac7-9234-3c3ee2ce7d0f) | ONEDRIVE_BASIC (da792a53-cbc0-4184-a10d-e544dd34b3c1)<br/>VISIO_CLIENT_SUBSCRIPTION (663a804f-1c30-4ff0-9915-9db84f0d1cea)<br/>VISIOONLINE (2bdbaf8f-738f-4ac7-9234-3c3ee2ce7d0f) |
 | WINDOWS 10 ENTERPRISE E3	| WIN10_PRO_ENT_SUB	| cb10e6cd-9da4-4992-867b-67546b1db821	| WIN10_PRO_ENT_SUB (21b439ba-a0ca-424f-a6cc-52f954a5b111) | WINDOWS 10 ENTERPRISE (21b439ba-a0ca-424f-a6cc-52f954a5b111)

articles/aks/api-server-authorized-ip-ranges.md

@@ -216,13 +216,13 @@ To enable API server authorized IP ranges, you provide a list of authorized IP a
 
 Use [az aks update][az-aks-update] command and specify the *--api-server-authorized-ip-ranges* to allow. These IP address ranges are usually address ranges used by your on-premises networks. Add the public IP address of your own Azure firewall obtained in the previous step, such as *20.42.25.196/32*.
 
-The following example enables API server authorized IP ranges on the cluster named *myAKSCluster* in the resource group named *myResourceGroup*. The IP address ranges to authorize are *20.42.25.196/32* (the Azure firewall public IP address), then *172.0.0.10/16* and *168.10.0.10/18*:
+The following example enables API server authorized IP ranges on the cluster named *myAKSCluster* in the resource group named *myResourceGroup*. The IP address ranges to authorize are *20.42.25.196/32* (the Azure firewall public IP address), then *172.0.0.0/16* and *168.10.0.0/18*:
 
 ```azurecli-interactive
 az aks update \
     --resource-group myResourceGroup \
     --name myAKSCluster \
-    --api-server-authorized-ip-ranges 20.42.25.196/32,172.0.0.10/16,168.10.0.10/18
+    --api-server-authorized-ip-ranges 20.42.25.196/32,172.0.0.0/16,168.10.0.0/18
 ```
 
 ## Update or disable authorized IP ranges

articles/aks/concepts-storage.md

@@ -30,7 +30,9 @@ Applications often need to be able to store and retrieve data. As Kubernetes typ
 Traditional volumes to store and retrieve data are created as Kubernetes resources backed by Azure Storage. You can manually create these data volumes to be assigned to pods directly, or have Kubernetes automatically create them. These data volumes can use Azure Disks or Azure Files:
 
 - *Azure Disks* can be used to create a Kubernetes *DataDisk* resource. Disks can use Azure Premium storage, backed by high-performance SSDs, or Azure Standard storage, backed by regular HDDs. For most production and development workloads, use Premium storage. Azure Disks are mounted as *ReadWriteOnce*, so are only available to a single node. For storage volumes that can be accessed by multiple nodes simultaneously, use Azure Files.
-- *Azure Files* can be used to mount an SMB 3.0 share backed by an Azure Storage account to pods. Files let you share data across multiple nodes and pods. Currently, Files can only use Azure Standard storage backed by regular HDDs.
+- *Azure Files* can be used to mount an SMB 3.0 share backed by an Azure Storage account to pods. Files let you share data across multiple nodes and pods. Files can use Azure Standard storage backed by regular HDDs, or Azure Premium storage, backed by high-performance SSDs.
+> [!NOTE] 
+> Azure Files support premium storage in AKS clusters that run Kubernetes 1.13 or higher.
 
 In Kubernetes, volumes can represent more than just a traditional disk where information can be stored and retrieved. Kubernetes volumes can also be used as a way to inject data into a pod for use by the containers. Common additional volume types in Kubernetes include:
 

articles/aks/tutorial-kubernetes-prepare-app.md

@@ -101,7 +101,7 @@ Stop and remove the container instances and resources with the [docker-compose d
 docker-compose down
 ```
 
-When the local application has been removed, you have a Docker image that contains the Azure Vote application, *azure-front-front*, for use with the next tutorial.
+When the local application has been removed, you have a Docker image that contains the Azure Vote application, *azure-vote-front*, for use with the next tutorial.
 
 ## Next steps
 

articles/automation/automation-update-management.md

@@ -17,7 +17,7 @@ You can use the Update Management solution in Azure Automation to manage operati
 You can enable Update Management for virtual machines directly from your Azure Automation account. To learn how to enable Update Management for virtual machines from your Automation account, see [Manage updates for multiple virtual machines](manage-update-multi.md). You can also enable Update Management for a virtual machine from the virtual machine page in the Azure portal. This scenario is available for [Linux](../virtual-machines/linux/tutorial-monitoring.md#enable-update-management) and [Windows](../virtual-machines/windows/tutorial-monitoring.md#enable-update-management) virtual machines.
 
 > [!NOTE]
-> The Update Management solution requires linking a Log Analytics workspace to your Automation account. For a definitive list of supported regions, see [https://docs.microsoft.com/en-us/azure/automation/how-to/region-mappings]. The region mappings do not affect the ability to manage virtual machines in a
+> The Update Management solution requires linking a Log Analytics workspace to your Automation account. For a definitive list of supported regions, see [Azure Workspace mappings](./how-to/region-mappings.md). The region mappings do not affect the ability to manage virtual machines in a
 > separate region than your Automation account.
 
 [!INCLUDE [azure-monitor-log-analytics-rebrand](../../includes/azure-monitor-log-analytics-rebrand.md)]

articles/azure-functions/functions-bindings-signalr-service.md

@@ -276,14 +276,15 @@ The following example adds a user to a group.
 [FunctionName("addToGroup")]
 public static Task AddToGroup(
     [HttpTrigger(AuthorizationLevel.Anonymous, "post")]HttpRequest req,
-    string userId,
+    ClaimsPrincipal claimsPrincipal,
     [SignalR(HubName = "chat")]
         IAsyncCollector<SignalRGroupAction> signalRGroupActions)
 {
+    var userIdClaim = claimsPrincipal.FindFirst(ClaimTypes.NameIdentifier);
     return signalRGroupActions.AddAsync(
         new SignalRGroupAction
         {
-            UserId = userId,
+            UserId = userIdClaim.Value,
             GroupName = "myGroup",
             Action = GroupAction.Add
         });
@@ -298,20 +299,24 @@ The following example removes a user from a group.
 [FunctionName("removeFromGroup")]
 public static Task RemoveFromGroup(
     [HttpTrigger(AuthorizationLevel.Anonymous, "post")]HttpRequest req,
-    string userId,
+    ClaimsPrincipal claimsPrincipal,
     [SignalR(HubName = "chat")]
         IAsyncCollector<SignalRGroupAction> signalRGroupActions)
 {
+    var userIdClaim = claimsPrincipal.FindFirst(ClaimTypes.NameIdentifier);
     return signalRGroupActions.AddAsync(
         new SignalRGroupAction
         {
-            UserId = userId,
+            UserId = userIdClaim.Value,
             GroupName = "myGroup",
             Action = GroupAction.Remove
         });
 }
 ```
 
+> [!NOTE]
+> In order to get the `ClaimsPrincipal` correctly bound, you must have configured the authentication settings in Azure Functions.
+
 ### 2.x JavaScript send message output examples
 
 #### Broadcast to all clients

articles/azure-monitor/insights/solution-office-365.md

@@ -565,12 +565,12 @@ These records are created when an Active Directory user attempts to log on.
 
 | Property | Description |
 |:--- |:--- |
-| OfficeWorkload | AzureActiveDirectory |
-| RecordType     | AzureActiveDirectoryAccountLogon |
-| Application | The application that triggers the account login event, such as Office 15. |
-| Client | Details about the client device, device OS, and device browser that was used for the of the account login event. |
-| LoginStatus | This property is from OrgIdLogon.LoginStatus directly. The mapping of various interesting logon failures could be done by alerting algorithms. |
-| UserDomain | The Tenant Identity Information (TII). | 
+| `OfficeWorkload` | AzureActiveDirectory |
+| `RecordType`     | AzureActiveDirectoryAccountLogon |
+| `Application` | The application that triggers the account login event, such as Office 15. |
+| `Client` | Details about the client device, device OS, and device browser that was used for the of the account login event. |
+| `LoginStatus` | This property is from OrgIdLogon.LoginStatus directly. The mapping of various interesting logon failures could be done by alerting algorithms. |
+| `UserDomain` | The Tenant Identity Information (TII). | 
 
 
 ### Azure Active Directory
@@ -748,4 +748,4 @@ The following table provides sample log searches for update records collected by
 
 * Use [log queries in Azure Monitor](../log-query/log-query-overview.md) to view detailed update data.
 * [Create your own dashboards](../learn/tutorial-logs-dashboards.md) to display your favorite Office 365 search queries.
-* [Create alerts](../platform/alerts-overview.md) to be proactively notified of important Office 365 activities.  
+* [Create alerts](../platform/alerts-overview.md) to be proactively notified of important Office 365 activities.  

articles/azure-monitor/log-query/string-operations.md

@@ -25,11 +25,11 @@ ms.author: bwren
 
 This article describes how to edit, compare, search in and perform a variety of other operations on strings.
 
-Each character in a string has an index number, according to its location. The first character is at index 0, the next character is 1, and so one. Different string functions use index numbers as shown in the following sections. Many of the following examples use the **print** command for to demonstrate string manipulation without using a specific data source.
+Each character in a string has an index number, according to its location. The first character is at index 0, the next character is 1, and so on. Different string functions use index numbers as shown in the following sections. Many of the following examples use the **print** command for to demonstrate string manipulation without using a specific data source.
 
 
 ## Strings and escaping them
-String values are wrapped with either with single or double quote characters. Backslash (\) is used to escape characters to the character following it, such as \t for tab, \n for newline, and \" the quote character itself.
+String values are wrapped with either with single or double quote characters. Backslash (\\) is used to escape characters to the character following it, such as \t for tab, \n for newline, and \" the quote character itself.
 
 ```Kusto
 print "this is a 'string' literal in double \" quotes"
@@ -85,7 +85,7 @@ Operator       |Description                         |Case-Sensitive|Example (yie
 
 ## countof
 
-Counts occurrences of a substring in a string. Can match plain strings or use regex. Plain string matches may overlap while regex matches don't.
+Counts occurrences of a substring in a string. Can match plain strings or use regex. Plain string matches may overlap while regex matches do not.
 
 ### Syntax
 ```
@@ -124,7 +124,7 @@ print countof("abcabc", "a.c", "regex");  // result: 2
 
 ## extract
 
-Gets a match for a regular expression from a given string. Optionally also converts the extracted substring the specified type.
+Gets a match for a regular expression from a given string. Optionally also converts the extracted substring to the specified type.
 
 ### Syntax
 

articles/azure-monitor/platform/alert-management-solution.md

@@ -84,26 +84,26 @@ The solution does import alerts from System Center Operations Manager and create
 
 | Property | Description |
 |:--- |:--- |
-| Type |*Alert* |
-| SourceSystem |*OpsManager* |
-| AlertContext |Details of the data item that caused the alert to be generated in XML format. |
-| AlertDescription |Detailed description of the alert. |
-| AlertId |GUID of the alert. |
-| AlertName |Name of the alert. |
-| AlertPriority |Priority level of the alert. |
-| AlertSeverity |Severity level of the alert. |
-| AlertState |Latest resolution state of the alert. |
-| LastModifiedBy |Name of the user who last modified the alert. |
-| ManagementGroupName |Name of the management group where the alert was generated. |
-| RepeatCount |Number of times the same alert was generated for the same monitored object since being resolved. |
-| ResolvedBy |Name of the user who resolved the alert. Empty if the alert has not yet been resolved. |
-| SourceDisplayName |Display name of the monitoring object that generated the alert. |
-| SourceFullName |Full name of the monitoring object that generated the alert. |
-| TicketId |Ticket ID for the alert if the System Center Operations Manager environment is integrated with a process for assigning tickets for alerts.  Empty of no ticket ID is assigned. |
-| TimeGenerated |Date and time that the alert was created. |
-| TimeLastModified |Date and time that the alert was last changed. |
-| TimeRaised |Date and time that the alert was generated. |
-| TimeResolved |Date and time that the alert was resolved. Empty if the alert has not yet been resolved. |
+| `Type` |*Alert* |
+| `SourceSystem` |*OpsManager* |
+| `AlertContext` |Details of the data item that caused the alert to be generated in XML format. |
+| `AlertDescription` |Detailed description of the alert. |
+| `AlertId` |GUID of the alert. |
+| `AlertName` |Name of the alert. |
+| `AlertPriority` |Priority level of the alert. |
+| `AlertSeverity` |Severity level of the alert. |
+| `AlertState` |Latest resolution state of the alert. |
+| `LastModifiedBy` |Name of the user who last modified the alert. |
+| `ManagementGroupName` |Name of the management group where the alert was generated. |
+| `RepeatCount` |Number of times the same alert was generated for the same monitored object since being resolved. |
+| `ResolvedBy` |Name of the user who resolved the alert. Empty if the alert has not yet been resolved. |
+| `SourceDisplayName` |Display name of the monitoring object that generated the alert. |
+| `SourceFullName` |Full name of the monitoring object that generated the alert. |
+| `TicketId` |Ticket ID for the alert if the System Center Operations Manager environment is integrated with a process for assigning tickets for alerts.  Empty of no ticket ID is assigned. |
+| `TimeGenerated` |Date and time that the alert was created. |
+| `TimeLastModified` |Date and time that the alert was last changed. |
+| `TimeRaised` |Date and time that the alert was generated. |
+| `TimeResolved` |Date and time that the alert was resolved. Empty if the alert has not yet been resolved. |
 
 ## Sample log searches
 The following table provides sample log searches for alert records collected by this solution: 

articles/backup/backup-configure-vault.md

@@ -27,7 +27,7 @@ In this article you learn how to:
 The MARS agent is used by Azure Backup to back up files, folders, and system state from on-premises machines and Azure VMs to a backup Recovery Services vault in Azure. You can run the agent as follows:
 
 - Run the agent directly on on-premises Windows machines so that they can back up directly to a backup Recovery Services vault in Azure.
-- Run the agent Azure VMs running Windows (side-by-side with the Azure VM backup extension) to back up specific files and folders on the VM.
+- Run the agent on Azure VMs running Windows (side-by-side with the Azure VM backup extension) to back up specific files and folders on the VM.
 - Run the agent on a Microsoft Azure Backup Server (MABS) or a System Center Data Protection - Manager (DPM) server. In this scenario, machines and workloads back up to MABS/DPM, and then MABS/DPM backs up to a vault in Azure using the MARS agent.
 What you can back up depends on where the agent is installed.