Merge pull request #175628 from MicrosoftDocs/repo_sync_working_branch

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

Author: huypub

articles/active-directory/app-provisioning/application-provisioning-quarantine-status.md

@@ -66,7 +66,7 @@ A job can go into quarantine regardless of failure counts for issues such as adm
 - If more than 40% of provisioning events fail, or there are more than 40,000 failures, the provisioning job will go into quarantine. Reference failures won't be counted as part of the 40% threshold or 40,000 threshold. For example, failure to update a manager or a group member is a reference failure.
 - A job where 45,000 users were unsuccessfully provisioned would lead to quarantine as it exceeds the 40,000 threshold.
 - A job where 30,000 users failed provisioning and 5,000 were successful would lead to quarantine as it exceeds the 40% threshold and 5,000 minimum.
-- A job with 20,000 failures and 100,000 success wouldn't go into quarantine because it doe not exceed the 40% failure threshold or the 40,000 failure max.  
+- A job with 20,000 failures and 100,000 success wouldn't go into quarantine because it does not exceed the 40% failure threshold or the 40,000 failure max.  
 - There's an absolute threshold of 60,000 failures that accounts for both reference and non-reference failures. For example, 40,000 users failed to be provisioned and 21,000 manager updates failed. The total is 61,000 failures and exceeds the 60,000 limit.
 
 

articles/active-directory/develop/msal-net-xamarin-ios-considerations.md

@@ -76,6 +76,29 @@ When you use the `WithIosKeychainSecurityGroup()` API, MSAL automatically append
 
 For more information, see the [iOS entitlements documentation](https://developer.apple.com/documentation/security/keychain_services/keychain_items/sharing_access_to_keychain_items_among_a_collection_of_apps).
 
+#### Troubleshooting KeyChain access
+
+If you get an error message similar to "The application cannot access the iOS keychain for the application publisher (the TeamId is null)", this means MSAL is not able to access the KeyChain. This is a configuration issue. To troubleshoot, try to access the KeyChain on your own, for example: 
+
+```csharp
+var queryRecord = new SecRecord(SecKind.GenericPassword)
+{
+    Service = "",
+    Account = "SomeTeamId",
+    Accessible = SecAccessible.Always
+};
+
+SecRecord match = SecKeyChain.QueryAsRecord(queryRecord, out SecStatusCode resultCode);
+
+if (resultCode == SecStatusCode.ItemNotFound)
+{
+    SecKeyChain.Add(queryRecord);
+    match = SecKeyChain.QueryAsRecord(queryRecord, out resultCode);
+}
+
+// Make sure that  resultCode == SecStatusCode.Success
+```
+
 ### Enable token cache sharing across iOS applications
 
 Starting in MSAL 2.x, you can specify a keychain access group to persist the token cache across multiple applications. This setting enables you to share the token cache among several applications that have the same keychain access group. You can share the token cache among [ADAL.NET](https://aka.ms/adal-net) applications, MSAL.NET Xamarin.iOS applications, and native iOS applications that were developed in [ADAL.objc](https://github.com/AzureAD/azure-activedirectory-library-for-objc) or [MSAL.objc](https://github.com/AzureAD/microsoft-authentication-library-for-objc).

articles/active-directory/develop/tutorial-v2-react.md

@@ -93,7 +93,7 @@ In the [Redirect URI: MSAL.js 2.0 with auth code flow](scenario-spa-app-registra
     export const msalConfig = {
       auth: {
         clientId: "Enter_the_Application_Id_Here",
-        authority: "Enter_the_Cloud_Instance_Id_Here/Enter_the_Tenant_Info_Here",
+        authority: "Enter_the_Cloud_Instance_Id_Here/Enter_the_Tenant_Info_Here", // This is a URL (e.g. https://login.microsoftonline.com/{your tenant ID})
         redirectUri: "Enter_the_Redirect_Uri_Here",
       },
       cache: {

articles/aks/use-wasi-node-pools.md

@@ -8,7 +8,7 @@ ms.date: 10/12/2021
 
 # Create WebAssembly System Interface (WASI) node pools in Azure Kubernetes Service (AKS) to run your WebAssembly (WASM) workload (preview)
 
-[WebAssembly (WASM)][wasm] is a binary format that is optimized for fast download and maximum execution speed in a WASM runtime. A WASM runtime is designed to run on a target architecture and execute WebAssebmlies in a sandbox, isolated from the host computer, at near-native performance. By default, WebAssebmlies can't access resources on the host outside of the sandbox unless it is explicitly allowed, and they can't communicate over sockets to access things environment variables or HTTP traffic. The [WebAssembly System Interface (WASI)][wasi] standard defines an API for WASM runtimes to provide access to WebAssebmlies to the environment and resources outside the host using a capabilities model. [Krustlet][krustlet] is an open-source project that allows WASM modules to be run on Kubernetes. Krustlet creates a kubelet that runs on nodes with a WASM/WASI runtime. AKS allows you to create node pools that run WASM assemblies using nodes with WASM/WASI runtimes and Krustlets.
+[WebAssembly (WASM)][wasm] is a binary format that is optimized for fast download and maximum execution speed in a WASM runtime. A WASM runtime is designed to run on a target architecture and execute WebAssemblies in a sandbox, isolated from the host computer, at near-native performance. By default, WebAssemblies can't access resources on the host outside of the sandbox unless it is explicitly allowed, and they can't communicate over sockets to access things environment variables or HTTP traffic. The [WebAssembly System Interface (WASI)][wasi] standard defines an API for WASM runtimes to provide access to WebAssemblies to the environment and resources outside the host using a capabilities model. [Krustlet][krustlet] is an open-source project that allows WASM modules to be run on Kubernetes. Krustlet creates a kubelet that runs on nodes with a WASM/WASI runtime. AKS allows you to create node pools that run WASM assemblies using nodes with WASM/WASI runtimes and Krustlets.
 
 ## Before you begin
 
@@ -319,4 +319,4 @@ az aks nodepool delete --name mywasipool -g myresourcegroup --cluster-name myaks
 [dockerhub-callout]: ../container-registry/buffer-gate-public-content.md
 [install-azure-cli]: /cli/azure/install-azure-cli
 [use-multiple-node-pools]: use-multiple-node-pools.md
-[use-system-pool]: use-system-pools.md
+[use-system-pool]: use-system-pools.md

articles/cognitive-services/Computer-vision/overview-ocr.md

@@ -28,7 +28,7 @@ This documentation contains the following types of articles:
 
 ## Read API 
 
-The Computer Vision [Read API](https://centraluseuap.dev.cognitive.microsoft.com/docs/services/computer-vision-v3-2/operations/5d986960601faab4bf452005) is Azure's latest OCR technology ([learn what's new](./whats-new.md)) that extracts printed text (in several languages), handwritten text (English only), digits, and currency symbols from images and multi-page PDF documents. It's optimized to extract text from text-heavy images and multi-page PDF documents with mixed languages. It supports detecting both printed and handwritten text in the same image or document.
+The Computer Vision [Read API](https://centraluseuap.dev.cognitive.microsoft.com/docs/services/computer-vision-v3-2/operations/5d986960601faab4bf452005) is Azure's latest OCR technology ([learn what's new](./whats-new.md)) that extracts printed text (in several languages), handwritten text (in several languages), digits, and currency symbols from images and multi-page PDF documents. It's optimized to extract text from text-heavy images and multi-page PDF documents with mixed languages. It supports detecting both printed and handwritten text in the same image or document.
 
 ![How OCR converts images and documents into structured output with extracted text](./Images/how-ocr-works.svg)
 

articles/cognitive-services/Speech-Service/includes/how-to/conversation-transcription/real-time-javascript.md

@@ -84,16 +84,8 @@ This sample code does the following:
     var region = "your-region";
     var filepath = "audio-file-to-transcribe.wav"; // 8-channel audio
 
-    // create the push stream and write file to it
-    var pushStream = sdk.AudioInputStream.createPushStream();
-    fs.createReadStream(filepath).on('data', function(arrayBuffer) {
-        pushStream.write(arrayBuffer.slice());
-    }).on('end', function() {
-        pushStream.close();
-    });
-    
     var speechTranslationConfig = sdk.SpeechTranslationConfig.fromSubscription(subscriptionKey, region);
-    var audioConfig = sdk.AudioConfig.fromStreamInput(pushStream);
+    var audioConfig = sdk.AudioConfig.fromWavFileInput(fs.readFileSync(filepath));
     speechTranslationConfig.setProperty("ConversationTranscriptionInRoomAndOnline", "true");
 
     // en-us by default. Adding this code to specify other languages, like zh-cn.

articles/cognitive-services/Speech-Service/tutorial-voice-enable-your-bot-speech-sdk.md

@@ -231,66 +231,69 @@ You'll need to make a small configuration change so that your bot can communicat
 
 ## Create a channel registration
 
-Now that you've created an Azure App Service to host your bot, the next step is to create a **Bot Channels Registration**. Creating a channel registration is a prerequisite for registering your bot with Bot Framework channels, including Direct Line Speech channel. If you'd like to learn more about how bots use channels, see [Connect a bot to channels](/azure/bot-service/bot-service-manage-channels).
+Now that you've created an Azure App Service to host your bot, the next step is to create an **Azure Bot**. Creating a channel registration is a prerequisite for registering your bot with Bot Framework channels, including Direct Line Speech channel. If you'd like to learn more about how bots use channels, see [Connect a bot to channels](/azure/bot-service/bot-service-manage-channels).
 
-1. <a href="https://ms.portal.azure.com/#create/Microsoft.BotServiceConnectivityGalleryPackage" target="_blank">Create an Azure Bot Channels Registration </a>
-2. You'll be prompted to provide some information:
+1. <a href="https://ms.portal.azure.com/#create/Microsoft.AzureBot" target="_blank">Create an Azure Bot</a>
+1. You'll be prompted to provide some information:
    * For **Bot handle**, enter **SpeechEchoBotTutorial-BotRegistration-####** and replace **####** with your a number of your choice. Note that Bot handle must be globally unique. If you enter a Bot handle but get the error message _The requested bot ID is not available_, then pick a different number. In the examples below we used 8726
    * For **Subscription**, select **Free Trial**.
    * For **Resource group**, select **SpeechEchoBotTutorial-ResourceGroup**.
-   * For **Location**, select **West US**.
-     * For **Pricing tier**, select **F0**.
-     * For **Messaging endpoint**, enter the URL for your web app with the `/api/messages` path appended at the end. For example: if your globally unique App Name was **EchoBot20190805125647**, your messaging endpoint would be: `https://EchoBot20190805125647.azurewebsites.net/api/messages/`.
-     * For **Application insights**, you can set this to **Off**. For more information, see [Bot analytics](/azure/bot-service/bot-service-manage-analytics).
-     * Ignore **Auto create App ID and password**.
-5. At the bottom of the **Bot Channels Registration** blade, click **Create**.
+     * For **Location**, select **West US**.
+   * For **Pricing tier**, select **F0**.
+   * Ignore **Auto create App ID and password**.
+1. At the bottom of the **Azure Bot** blade, select **Create**.
+1. After you create the resource, open your **SpeechEchoBotTutorial-BotRegistration-####** resource in the Azure portal.
+1. From the **Settings** navigation, select **Configuration**.
+1. For **Messaging endpoint**, enter the URL for your web app with the `/api/messages` path appended. For example, if your globally unique app name was **EchoBot20190805125647**, your messaging endpoint would be `https://EchoBot20190805125647.azurewebsites.net/api/messages/`.
 
 At this point, check your Resource Group **SpeechEchoBotTutorial-ResourceGroup** in the Azure portal. It should now show at least four resources:
 
 | Name | Type  | Location |
 |------|-------|----------|
 | EchoBot20190805125647 | App Service | West US |
 | SpeechEchoBotTutorial-AppServicePlan | App Service plan | West US |
-| SpeechEchoBotTutorial-BotRegistration-8726 | Bot Channels Registration | Global |
+| SpeechEchoBotTutorial-BotRegistration-8726 | Azure Bot | Global |
 | SpeechEchoBotTutorial-Speech | Cognitive Services | West US |
 
 > [!IMPORTANT]
-> The Bot Channels Registration resource will show the Global region even though you selected West US. This is expected.
+> The Azure Bot resource will show the Global region, even though you selected West US. This is expected.
 
 ## Optional: Test in web chat
 
-The Azure Bot Channels Registration page has a **Test in Web Chat** option under **Bot Management**. It will not work by default with your bot, since web chat needs to authenticate against your bot. If you would like to test your deployed bot with text input, follow the steps below. Note that these steps are optional, and are not required in order to continue with the next steps of the tutorial. 
+The Azure Bot page has a **Test in Web Chat** option under **Settings**. It will not work by default with your bot because web chat needs to authenticate against your bot. If you would like to test your deployed bot with text input, follow the steps below. Note that these steps are optional and are not required for you to continue with the next steps of the tutorial. 
 
 1. Locate and open your **EchoBotTutorial-BotRegistration-####** resource in the [Azure portal](https://portal.azure.com)
-1. From the **Bot management** navigation, select **Settings**. Copy the value under **Microsoft App ID**
+1. From the **Settings** navigation, select **Configuration**. Copy the value under **Microsoft App ID**
 1. Open the Visual Studio EchoBot solution. In the solution explorer, locate and double click on **appsettings.json**
 1. Replace the empty string next to **MicrosoftAppId** in the JSON file with the copied ID value
-1. Got back to the Azure portal, in **Bot management** navigation, select **Settings**, and click on **(Manage)** next to **Microsoft App ID**
+1. Got back to the Azure portal, in **Settings** navigation, select **Configuration**, and click on **(Manage)** next to **Microsoft App ID**
 1. Click on **New client secret**. Add a description (e.g. "web chat") and click **Add**. Copy the new secret
 1. Replace the empty string next to **MicrosoftAppPassword** in the JSON file with the copied secret value
 1. Save the JSON file. It should look something like this:
-```json
-{
-  "MicrosoftAppId": "3be0abc2-ca07-475e-b6c3-90c4476c4370",
-  "MicrosoftAppPassword": "-zRhJZ~1cnc7ZIlj4Qozs_eKN.8Cq~U38G"
-}
-```
-9. Re-publish the app (right-click on **EchoBot** project in Visual Studio solution explorer, select **Publish...** and click on the **Publish** button)
-10. Now you are ready to test the bot in web chat!
+
+   ```json
+   {
+     "MicrosoftAppId": "3be0abc2-ca07-475e-b6c3-90c4476c4370",
+     "MicrosoftAppPassword": "-zRhJZ~1cnc7ZIlj4Qozs_eKN.8Cq~U38G"
+   }
+   ```
+
+1. Republish the app (right-click on **EchoBot** project in Visual Studio Solution Explorer, select **Publish...** and click on the **Publish** button)
+1. Now you are ready to test the bot in web chat!
 
 ## Register the Direct Line Speech channel
 
 Now it's time to register your bot with the Direct Line Speech channel. This channel creates a connection between your bot and a client app compiled with the Speech SDK.
 
 1. Locate and open your **SpeechEchoBotTutorial-BotRegistration-####** resource in the [Azure portal](https://portal.azure.com).
-1. From the **Bot management** navigation, select **Channels**.
+1. From the **Settings** navigation, select **Channels**.
    * Under **More channels**, click **Direct Line Speech**.
    * Review the text on the page titled **Configure Direct line Speech**, then expand the **Cognitive service account** drop-down menu.
    * Select the speech resource you created earlier (e.g., **SpeechEchoBotTutorial-Speech**) from the menu to associate your bot to your speech subscription key.
    * Ignore the rest of the optional fields.
    * Click **Save**.
 
-1. From the **Bot management** navigation, click **Settings**.
+1. From the **Settings** navigation, click **Configuration**.
    * Check the box labeled **Enable Streaming Endpoint**. This is needed to create a communication protocol built on web sockets between your bot and the Direct Line Speech channel.
    * Click **Save**.
 

articles/cosmos-db/graph/supply-chain-traceability-solution.md

@@ -25,19 +25,20 @@ After reading this article, you will learn:
 
 ## Overview
 
-In the food supply chain, product traceability is the ability to ‘track and trace’ them across the supply chain throughout the product’s lifecycle. The supply chain includes supply, manufacturing, and distribution. Traceability is vital for food safety, brand, and regulatory exposure. In the past some organizations failed to track and trace products effectively in their supply chain, resulting in expensive recalls, fines, and consumer health issues.
+In the food supply chain, product traceability is the ability to 'track and trace' them across the supply chain throughout the product’s lifecycle. The supply chain includes supply, manufacturing, and distribution. Traceability is vital for food safety, brand, and regulatory exposure. In the past, some organizations failed to track and trace products effectively in their supply chain, resulting in expensive recalls, fines, and consumer health issues. The traceability solutions had to address the needs of data harmonization, data ingestion at different velocity and veracity, and, more importantly, follow the inventory cycle, objectives that weren't possible with traditional platforms.
 
-Infosys’s traceability solution, developed with Azure capabilities such as application services, integration services and database services, provides vital capabilities to:
+Infosys's traceability solution, developed with Azure capabilities such as application services, integration services and database services, provides vital capabilities to:
 
 * Connect to factories, warehouses/distribution centers.
 * Ingest/process parallel stock movement events.
 * A knowledge graph, which shows connections between raw material, batch, finish goods (FG) pallets, multi-level parent/child relationship of pallets, goods movement.
-* Portal with search to trace and track pallets.
+* User portal with a search capability range of wildcard search to specific keyword search.
 * Identify impacts of a quality incident such as impacted raw material batch, pallets affected, location of the pallets.
+* Ability to have the history of events captured across multiple markets, including product recall information.
 
 ## Solution architecture
 
-Supply chain traceability commonly shares patterns in ingesting pallet movements, handing quality incidents, and tracing/analyzing store data. First, these systems need to ingest bursts of data from factory/Warehouse Management Systems systems that spread across geographies. Next, these systems process and analyze streaming data to derive complex relationships between raw material, production batches, finished good pallets and complex parent/child relationships (co-pack/repack.). Then the system requires to store intricate relationships between raw-material, finished goods, pallets necessary for traceability. A user portal with search capability allows the users to track and trace products in the supply chain network.
+Supply chain traceability commonly shares patterns in ingesting pallet movements, handing quality incidents, and tracing/analyzing store data. First, these systems need to ingest bursts of data from factory and warehouse management systems that cross geographies. Next, these systems process and analyze streaming data to derive complex relationships between raw material, production batches, finished good pallets and complex parent/child relationships (co-pack/repack). Then, the system must store information about the intricate relationships between raw material, finished goods, and pallets, all necessary for traceability. A user portal with search capability allows the users to track and trace products in the supply chain network. These services enable the end-to-end traceability solution that supports cloud-native, API-first, and data-driven capabilities.
 
 Microsoft Azure offers rich services that can be applied for traceability use cases, including Azure Cosmos DB, Azure Event Hubs, Azure API Management, Azure App Service, Azure SignalR, Azure Synapse Analytics, and Power BI.