Merge pull request #159017 from MicrosoftDocs/master

Merge master to live, 4 AM

Author: ttorble

articles/app-service/networking/private-endpoint.md

@@ -149,6 +149,6 @@ We are improving Private Link feature and Private Endpoint regularly, check [thi
 [howtoguide2]: ../scripts/cli-deploy-privateendpoint.md
 [howtoguide3]: ../scripts/powershell-deploy-private-endpoint.md
 [howtoguide4]: ../scripts/template-deploy-private-endpoint.md
-[howtoguide5]: https://github.com/Azure/azure-quickstart-templates/tree/master/101-webapp-privateendpoint-vnet-injection
+[howtoguide5]: https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.web/webapp-privateendpoint-vnet-injection
 [howtoguide6]: ../scripts/terraform-secure-backend-frontend.md
 [TiP]: https://docs.microsoft.com/azure/app-service/deploy-staging-slots#route-traffic

articles/automation/learn/automation-tutorial-runbook-textual-python2.md

@@ -18,9 +18,6 @@ This tutorial walks you through the creation of a [Python runbook](../automation
 > * Run and track the status of the runbook job
 > * Update the runbook to start an Azure virtual machine with runbook parameters
 
-> [!NOTE]
-> Using a webhook to start a Python runbook is not supported.
-
 ## Prerequisites
 
 To complete this tutorial, you need the following:

articles/azure-monitor/app/asp-net-core.md

@@ -21,7 +21,7 @@ The [Application Insights SDK for ASP.NET Core](https://nuget.org/packages/Micro
 * **Deployment method**: Framework dependent or self-contained.
 * **Web server**: IIS (Internet Information Server) or Kestrel.
 * **Hosting platform**: The Web Apps feature of Azure App Service, Azure VM, Docker, Azure Kubernetes Service (AKS), and so on.
-* **.NET Core version**: All officially [supported](https://dotnet.microsoft.com/download/dotnet-core) .NET Core versions.
+* **.NET Core version**: All officially [supported .NET Core versions](https://dotnet.microsoft.com/download/dotnet-core) that are not in preview.
 * **IDE**: Visual Studio, VS Code, or command line.
 
 > [!NOTE]

articles/azure-monitor/app/azure-web-apps.md

@@ -71,7 +71,7 @@ There are two ways to enable application monitoring for Azure App Services hoste
 # [ASP.NET Core](#tab/netcore)
 
 > [!IMPORTANT]
-> The following versions of ASP.NET Core are supported: ASP.NET Core 2.1 and 3.1. Versions 2.0, 2.2, and 3.0 have been retired and are no longer supported. Please upgrade to a [supported version](https://dotnet.microsoft.com/platform/support/policy/dotnet-core) of .NET Core for auto-instrumentation to work.
+> The following versions of ASP.NET Core are supported: ASP.NET Core 2.1, 3.1, and 5.0. Versions 2.0, 2.2, and 3.0 have been retired and are no longer supported. Please upgrade to a [supported version](https://dotnet.microsoft.com/platform/support/policy/dotnet-core) of .NET Core for auto-instrumentation to work.
 
 Targeting the full framework from ASP.NET Core, self-contained deployment, and Linux based applications are currently **not supported** with agent/extension based monitoring. ([Manual instrumentation](./asp-net-core.md) via code will work in all of the previous scenarios.)
 

articles/azure-netapp-files/azacsnap-troubleshoot.md

@@ -13,13 +13,13 @@ ms.workload: storage
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: troubleshooting
-ms.date: 04/21/2021
+ms.date: 05/17/2021
 ms.author: phjensen
 ---
 
 # Troubleshoot Azure Application Consistent Snapshot tool
 
-This article provides troubleshooting content for using the Azure Application Consistent Snapshot tool that you can use with Azure NetApp Files.
+This article provides troubleshooting content for using the Azure Application Consistent Snapshot tool that you can use with Azure NetApp Files and Azure Large Instance.
 
 The following are common issues that you may encounter while running the commands. Follow the resolution instructions mentioned to fix the issue. If you still encounter an issue, open a Service Request from Azure portal and assign the request into the SAP HANA Large Instance queue for Microsoft Support to respond.
 
@@ -58,7 +58,9 @@ When validating communication with Azure NetApp Files, communication might fail
 - (https://)management.azure.com:443
 - (https://)login.microsoftonline.com:443 
 
-## Failed communication with SAP HANA
+## Problems with SAP HANA
+
+### Running the test command fails
 
 When validating communication with SAP HANA by running a test with `azacsnap -c test --test hana` and it provides the following error:
 
@@ -95,7 +97,7 @@ Cannot get SAP HANA version, exiting with error: 127
     In this example, the `hdbsql` command isn't in the users `$PATH`.
 
     ```bash
-    hdbsql -n 172.18.18.50 - i 00 -U SCADMIN "select version from sys.m_database"
+    hdbsql -n 172.18.18.50 - i 00 -U AZACSNAP "select version from sys.m_database"
     ```
 
     ```output
@@ -110,17 +112,45 @@ Cannot get SAP HANA version, exiting with error: 127
     ```
 
     ```bash
-    hdbsql -n 172.18.18.50 -i 00 -U SCADMIN "select version from sys.m_database"
+    hdbsql -n 172.18.18.50 -i 00 -U AZACSNAP "select version from sys.m_database"
     ```
 
     ```output
-    * -10104: Invalid value for KEY (SCADMIN)
+    * -10104: Invalid value for KEY (AZACSNAP)
     ```
 
     > [!NOTE]
     > To permanently add to the user's `$PATH`, update the user's `$HOME/.profile` file
 
-## The `hdbuserstore` location
+### Insufficient privilege
+
+If running `azacsnap` presents an error such as `* 258: insufficient privilege`, check to ensure the appropriate privilege has been asssigned to the "AZACSNAP" database user (assuming this is the user created per the [installation guide](azacsnap-installation.md#enable-communication-with-sap-hana)).  Verify the user's current privilege with the following command:
+
+```bash
+hdbsql -U AZACSNAP "select GRANTEE,GRANTEE_TYPE,PRIVILEGE,IS_VALID,IS_GRANTABLE from sys.granted_privileges "' | grep -i -e GRANTEE -e azacsnap
+```
+
+```output
+GRANTEE,GRANTEE_TYPE,PRIVILEGE,IS_VALID,IS_GRANTABLE
+"AZACSNAP","USER","BACKUP ADMIN","TRUE","FALSE"
+"AZACSNAP","USER","CATALOG READ","TRUE","FALSE"
+"AZACSNAP","USER","CREATE ANY","TRUE","TRUE"
+```
+
+The error might also provide further information to help determine the required SAP HANA privileges, such as the output of `Detailed info for this error can be found with guid '99X9999X99X9999X99X99XX999XXX999' SQLSTATE: HY000`.  In this case follow SAP's instructions at [SAP Help Portal - GET_INSUFFICIENT_PRIVILEGE_ERROR_DETAILS](https://help.sap.com/viewer/b3ee5778bc2e4a089d3299b82ec762a7/2.0.05/en-US/9a73c4c017744288b8d6f3b9bc0db043.html) which recommends using the following SQL query to determine the detail on the required privilege.
+
+```sql
+CALL SYS.GET_INSUFFICIENT_PRIVILEGE_ERROR_DETAILS ('99X9999X99X9999X99X99XX999XXX999', ?)
+```
+
+```output
+GUID,CREATE_TIME,CONNECTION_ID,SESSION_USER_NAME,CHECKED_USER_NAME,PRIVILEGE,IS_MISSING_ANALYTIC_PRIVILEGE,IS_MISSING_GRANT_OPTION,DATABASE_NAME,SCHEMA_NAME,OBJECT_NAME,OBJECT_TYPE
+"99X9999X99X9999X99X99XX999XXX999","2021-01-01 01:00:00.180000000",120212,"AZACSNAP","AZACSNAP","DATABASE ADMIN or DATABASE BACKUP ADMIN","FALSE","FALSE","","","",""
+```
+
+In the example above, adding the 'DATABASE BACKUP ADMIN' privilege to the SYSTEMDB's AZACSNAP user, should resolve the insufficient privilege error.
+
+### The `hdbuserstore` location
 
 When setting up communication with SAP HANA, the `hdbuserstore` program is used to create the secure communication settings.  The `hdbuserstore` program is usually found under `/usr/sap/<SID>/SYS/exe/hdb/` or `/usr/sap/hdbclient`.  Normally the installer adds the correct location to the `azacsnap` user's `$PATH`.
 

articles/azure-percept/quickstart-percept-audio-setup.md

@@ -18,22 +18,22 @@ Azure Percept Audio works out of the box with Azure Percept DK. No unique setup
 - Azure Percept Audio
 - [Azure subscription](https://azure.microsoft.com/free/)
 - [Azure Percept DK setup experience](./quickstart-percept-dk-set-up.md): you connected your devkit to a Wi-Fi network, created an IoT Hub, and connected your devkit to the IoT Hub
-- Speaker or headphones that can connect to a 3.5mm audio jack (optional)
+- Speaker or headphones that can connect to a 3.5-mm audio jack (optional)
 
 ## Connecting your devices
 
 1. Connect the Azure Percept Audio device to the Azure Percept DK carrier board with the included Micro USB to USB Type-A cable. Connect the Micro USB end of the cable to the Audio interposer (developer) board and the Type-A end to the Percept DK carrier board.
 
-1. (Optional) connect your speaker or headphones to your Azure Percept Audio device via the audio jack, which is labeled "Line Out." This will allow you to hear audio responses.
+1. (Optional) connect your speaker or headphones to your Azure Percept Audio device via the audio jack, labeled "Line Out." This will allow you to hear audio responses.
 
-1. Power on the devkit. LED L02 on the Audio interposer board will change to blinking white to indicate that the device was powered on and that the Audio SoM is authenticating.
+1. Power on the devkit. LED L02 will change to blinking white, which indicates that the device was powered on and is authenticating.
 
-1. Wait for the authentication process to complete--this can take up to 3 minutes.
+1. Wait for the authentication process to complete, which takes up to 5 minutes.
 
-1. You are ready to begin prototyping when you see one of the following:
+1. You're ready to begin prototyping when you see one of the following LED states:
 
-    - LED L02 will change to solid white: this indicates that authentication is complete, and the devkit has not been configured with a keyword yet.
-    - All three LEDs turn blue: this indicates that authentication is complete, and the devkit is configured with a keyword.
+    - LED L02 will change to solid white, indicating that the authentication is complete and the devkit is configured without a keyword.
+    - All three LEDs turn blue, indicating that the authentication is complete and the devkit is configured with a keyword.
 
 ## Next steps
 

articles/azure-percept/quickstart-percept-dk-set-up.md

@@ -59,7 +59,7 @@ To verify if your Azure account is an “owner” or “contributor” within th
     > [!WARNING]
     > While connected to the Azure Percept DK Wi-Fi access point, your host computer will temporarily lose its connection to the Internet. Active video conference calls, web streaming, or other network-based experiences will be interrupted.
 
-1. Once connected to the dev kit’s Wi-Fi access point, the host computer will automatically launch the setup experience in a new browser window with **your.new.device/** in the address bar. If the tab does not open automatically, launch the setup experience by going to [http://10.1.1.1](http://10.1.1.1). Make sure your browser is signed in with the same Azure account credentials you intend to use with Azure Percept.
+1. Once connected to the dev kit’s Wi-Fi access point, the host computer will automatically launch the setup experience in a new browser window with **your.new.device/** in the address bar. If the tab does not open automatically, launch the setup experience by going to [http://10.1.1.1](http://10.1.1.1) in a web browser. Make sure your browser is signed in with the same Azure account credentials you intend to use with Azure Percept.
 
     :::image type="content" source="./media/quickstart-percept-dk-setup/main-01-welcome.png" alt-text="Welcome page.":::
 

articles/azure-percept/troubleshoot-audio-accessory-speech-module.md

@@ -13,6 +13,34 @@ ms.custom: template-how-to #Required; leave this attribute/value as-is.
 
 Use the guidelines below to troubleshoot voice assistant application issues.
 
+## Understanding Ear SoM LED indicators
+
+You can use LED indicators to understand which state your device is in. It takes around 4-5 minutes for the device to power on and the module to fully initialize. As it goes through initialization steps, you will see:
+
+1. Center white LED on (static): the device is powered on.
+1. Center white LED on (blinking): authentication is in progress.
+1. Center white LED on (static): the device is authenticated but keyword is not configured.​
+1. All three LEDs will change to blue once a demo was deployed and the device is ready to use.
+
+For more reference, see this article about [Azure Percept Audio button and LED behavior](./audio-button-led-behavior.md).
+
+### Troubleshooting LED issues
+- **If the center LED is solid white**, try [using a template to create a voice assistant](./tutorial-no-code-speech.md).
+- **If the center LED is always blinking**, it indicates an authentication issue. Try these troubleshooting steps:
+    - Make sure that your USB-A and micro USB connections are secured 
+    - Check to see if the [speech module is running](./troubleshoot-audio-accessory-speech-module.md#checking-runtime-status-of-the-speech-module)
+    - Restart the device
+    - [Collect logs](./troubleshoot-audio-accessory-speech-module.md#collecting-speech-module-logs) and attach them to a support request
+    - Check to see if your dev kit is running the latest software and apply an update if available.
+
+## Checking runtime status of the speech module
+
+Check if the runtime status of **azureearspeechclientmodule** shows as **running**. To locate the runtime status of your device modules, open the [Azure portal](https://portal.azure.com/) and navigate to **All resources** -> **[your IoT hub]** -> **IoT Edge** -> **[your device ID]**. Click the **Modules** tab to see the runtime status of all installed modules.
+
+:::image type="content" source="./media/troubleshoot-audio-accessory-speech-module/over-the-air-iot-edge-device-page.png" alt-text="Edge device page in the Azure portal.":::
+
+If the runtime status of **azureearspeechclientmodule** is not listed as **running**, click **Set modules** -> **azureearspeechclientmodule**. On the **Module Settings** page, set **Desired Status** to **running** and click **Update**.
+
 ## Collecting speech module logs
 
 To run these commands, [SSH into the dev kit](./how-to-ssh-into-percept-dk.md) and enter the commands into the SSH client prompt.
@@ -41,33 +69,15 @@ After redirecting output to a .txt file, copy the file to your host PC via SCP:
 scp [remote username]@[IP address]:[remote file path]/[file name].txt [local host file path]
 ```
 
-[local host file path] refers to the location on your host PC which you would like to copy the .txt file to. [remote username] is the SSH username chosen during the [setup experience](./quickstart-percept-dk-set-up.md).
-
-## Checking runtime status of the speech module
-
-Check if the runtime status of **azureearspeechclientmodule** shows as **running**. To locate the runtime status of your device modules, open the [Azure portal](https://portal.azure.com/) and navigate to **All resources** -> **[your IoT hub]** -> **IoT Edge** -> **[your device ID]**. Click the **Modules** tab to see the runtime status of all installed modules.
-
-:::image type="content" source="./media/troubleshoot-audio-accessory-speech-module/over-the-air-iot-edge-device-page.png" alt-text="Edge device page in the Azure portal.":::
-
-If the runtime status of **azureearspeechclientmodule** is not listed as **running**, click **Set modules** -> **azureearspeechclientmodule**. On the **Module Settings** page, set **Desired Status** to **running** and click **Update**.
-
-## Understanding Ear SoM LED indicators
-
-You can use LED indicators to understand which state you device is in. Usually it takes around 2 minutes for the module to fully initialize after the device powers on. As it goes through initialization steps, you will see:
-
-1. Center white LED on (static): the device is powered on.
-2. Center white LED on (blinking): authentication is in progress.
-3. All three LEDs will change to blue once the device is authenticated and ready to use.
-
-|LED|LED State|Ear SoM Status|
-|---|---------|--------------|
-|L02|1x white, static on|Power on |
-|L02|1x white, 0.5 Hz flashing|Authentication in progress |
-|L01 & L02 & L03|3x blue, static on|Waiting for keyword|
-|L01 & L02 & L03|LED array flashing, 20fps |Listening or speaking|
-|L01 & L02 & L03|LED array racing, 20fps|Thinking|
-|L01 & L02 & L03|3x red, static on |Mute|
+[local host file path] refers to the location on your host PC, which you would like to copy the .txt file to. [remote username] is the SSH username chosen during the [setup experience](./quickstart-percept-dk-set-up.md).
 
-## Next steps
+## Known issues
+- If using a free trial, the speech model may exceed the free trial price plan. In this case, the model will stop working without an error message.
+- If more than 5 IoT Edge devices are connected, the report (the text sent via telemetry to IoT Hub and Speech Studio) may be blocked.
+- If the device is in a different region than the resources, the report message may be delayed. 
 
-See the [general troubleshooting guide](./troubleshoot-dev-kit.md) for more information on troubleshooting your Azure Percept DK.
+## Useful links
+- [Azure Percept Audio setup](./quickstart-percept-audio-setup.md)
+- [Azure Percept Audio button and LED behavior](./audio-button-led-behavior.md)
+- [Create a voice assistant with Azure Percept DK and Azure Percept Audio](./tutorial-no-code-speech.md)
+- [Azure Percept DK general troubleshooting guide](./troubleshoot-dev-kit.md)

articles/azure-signalr/howto-use-managed-identity.md

@@ -79,7 +79,7 @@ We provide libraries and code samples that show how to handle token validation.
 
 Setting access token validation in Function App is easy and efficient without code works.
 
-1. In the **Authentication / Authorization** page, switch **App Service Authentication** to **On**.
+1. In the **Authentication (classic)** page, switch **App Service Authentication** to **On**.
 
 2. Select **Log in with Azure Active Directory** in **Action to take when request is not authenticated**.
 
@@ -94,6 +94,10 @@ Setting access token validation in Function App is easy and efficient without co
 
 After these settings, the Function App will reject requests without an access token in the header.
 
+> [!Important] 
+> To pass the authentication, the *Issuer Url* must match the *iss* claim in token. Currently, we only support v1 endpoint (see [v1.0 and v2.0](../active-directory/develop/access-tokens.md#v10-and-v20)), so the *Issuer Url* should look like `https://sts.windows.net/<tenant-id>/`. Check the *Issuer Url* configured in Azure Function. For **Authentication**, go to *Identity provider* -> *Edit* -> *Issuer Url* and for **Authentication (classic)**, go to *Azure Active Directory* -> *Advanced* -> *Issuer Url*
+
+
 ## Use a managed identity for Key Vault reference
 
 SignalR Service can access Key Vault to get secret using the managed identity.
@@ -109,4 +113,4 @@ Currently, this feature can be used in the following scenarios:
 
 ## Next steps
 
-- [Azure Functions development and configuration with Azure SignalR Service](signalr-concept-serverless-development-config.md)
+- [Azure Functions development and configuration with Azure SignalR Service](signalr-concept-serverless-development-config.md)

articles/cognitive-services/Anomaly-Detector/How-to/identify-anomalies.md

@@ -37,7 +37,7 @@ By sending your time series data at once, the API will generate a model using th
 
 To continuously detect anomalies on streaming data, use the following request URI with your latest data point: 
 
-`/timeseries/last/detect'`. 
+`/timeseries/last/detect`. 
 
 By sending new data points as you generate them, you can monitor your data in real time. A model will be generated with the data points you send, and the API will determine if the latest point in the time series is an anomaly.