Merge pull request #217362 from MicrosoftDocs/main

Publish to live, Monday 4 AM PST, 11/7

Author: ttorble

articles/active-directory-b2c/self-asserted-technical-profile.md

@@ -9,7 +9,7 @@ manager: CelesteDG
 ms.service: active-directory
 ms.workload: identity
 ms.topic: reference
-ms.date: 02/17/2022
+ms.date: 11/07/2022
 ms.author: kengaderdus
 ms.subservice: B2C
 ---
@@ -50,8 +50,6 @@ In a self-asserted technical profile, you can use the **InputClaims** and **Inpu
 
 ## Display claims
 
-The display claims feature is currently in **preview**.
-
 The **DisplayClaims** element contains a list of claims to be presented on the screen for collecting data from the user. To prepopulate the values of display claims, use the input claims that were previously described. The element may also contain a default value.
 
 The order of the claims in **DisplayClaims** specifies the order in which Azure AD B2C renders the claims on the screen. To force the user to provide a value for a specific claim, set the **Required** attribute of the **DisplayClaim** element to `true`.
@@ -133,7 +131,7 @@ Use output claims when:
 - **Claims are output by output claims transformation**.
 - **Setting a default value in an output claim** without collecting data from the user or returning the data from the validation technical profile. The `LocalAccountSignUpWithLogonEmail` self-asserted technical profile sets the **executed-SelfAsserted-Input** claim to `true`.
 - **A validation technical profile returns the output claims** - Your technical profile may call a validation technical profile that returns some claims. You may want to bubble up the claims and return them to the next orchestration steps in the user journey. For example, when signing in with a local account, the self-asserted technical profile named `SelfAsserted-LocalAccountSignin-Email` calls the validation technical profile named `login-NonInteractive`. This technical profile validates the user credentials and also returns the user profile. Such as 'userPrincipalName', 'displayName', 'givenName' and 'surName'.
-- **A display control returns the output claims** - Your technical profile may have a reference to a [display control](display-controls.md). The display control returns some claims, such as the verified email address. You may want to bubble up the claims and return them to the next orchestration steps in the user journey. The display control feature is currently in **preview**.
+- **A display control returns the output claims** - Your technical profile may have a reference to a [display control](display-controls.md). The display control returns some claims, such as the verified email address. You may want to bubble up the claims and return them to the next orchestration steps in the user journey. 
 
 The following example demonstrates the use of a self-asserted technical profile that uses both display claims and output claims.
 

articles/active-directory/develop/tutorial-v2-nodejs-desktop.md

@@ -52,7 +52,7 @@ Create a folder to host your application, for example *ElectronDesktopApp*.
 
     ```console
     npm init -y
-    npm install --save @azure/msal-node @microsoft/microsoft-graph-sdk isomorphic-fetch bootstrap jquery popper.js
+    npm install --save @azure/msal-node @microsoft/microsoft-graph-client isomorphic-fetch bootstrap jquery popper.js
     npm install --save-dev [email protected]
     ```
 

articles/active-directory/external-identities/user-flow-add-custom-attributes.md

@@ -8,10 +8,12 @@ manager: celestedg
 ms.service: active-directory
 ms.subservice: B2B
 ms.topic: how-to
-ms.date: 03/02/2021
+ms.date: 11/07/2022
 ms.author: mimart
-ms.custom: engagement-fy23, "it-pro"
+ms.custom: engagement-fy23, it-pro
 ms.collection: M365-identity-device-management
+
+# Customer intent: As a tenant administrator, I want to create custom attributes for the self-service sign-up user flows.
 ---
 
 # Define custom attributes for user flows
@@ -53,4 +55,5 @@ Once you've created a new user using a user flow that uses the newly created cus
 
 ## Next steps
 
-[Add a self-service sign-up user flow to an app](self-service-sign-up-user-flow.md)
+- [Add a self-service sign-up user flow to an app](self-service-sign-up-user-flow.md)
+- [Customize the user flow language](user-flow-customize-language.md)

articles/api-management/virtual-network-reference.md

@@ -30,6 +30,9 @@ When an API Management service instance is hosted in a VNet, the ports in the fo
 
 ### [stv2](#tab/stv2)
 
+>[!IMPORTANT]
+> When using `stv2`, it is required to assign a Network Security Group to your VNet in order for the Azure Load Balancer to work. Learn more in the [Azure Load Balancer documentation](/security/benchmark/azure/baselines/azure-load-balancer-security-baseline#network-security-group-support).
+
 | Source / Destination Port(s) | Direction          | Transport protocol |   Service tags <br> Source / Destination   | Purpose                                            | VNet type |
 |------------------------------|--------------------|--------------------|---------------------------------------|-------------------------------------------------------------|----------------------|
 | * / [80], 443                  | Inbound            | TCP                | Internet / VirtualNetwork           | **Client communication to API Management**                     | External only            |

articles/azure-functions/functions-develop-local.md

@@ -91,7 +91,7 @@ When you develop your functions locally, you need to take trigger and binding be
 
 ## Local storage emulator
 
-During local development, you can use the local [Azurite emulator](/azure/storage/common/storage-use-azurite.md) when testing functions with Azure Storage bindings (Queue Storage, Blob Storage, and Table Storage), without having to connect to remote storage services. Azurite integrates with Visual Studio Code and Visual Studio, and you can also run it from the command prompt using npm. For more information, see [Use the Azurite emulator for local Azure Storage development](/storage/common/storage-use-azurite.md).
+During local development, you can use the local [Azurite emulator](../storage/common/storage-use-azurite.md) when testing functions with Azure Storage bindings (Queue Storage, Blob Storage, and Table Storage), without having to connect to remote storage services. Azurite integrates with Visual Studio Code and Visual Studio, and you can also run it from the command prompt using npm. For more information, see [Use the Azurite emulator for local Azure Storage development](../storage/common/storage-use-azurite.md).
 
 The following setting in the `Values` collection of the local.settings.json file tells the local Functions host to use Azurite for the default `AzureWebJobsStorage` connection:
 

articles/cognitive-services/Anomaly-Detector/How-to/streaming-inference.md

@@ -44,7 +44,7 @@ A sample request:
 {
   "variables": [
     {
-      "variableName": "Variable_1",
+      "variable": "Variable_1",
       "timestamps": [
         "2021-01-01T00:00:00Z",
         "2021-01-01T00:01:00Z",
@@ -59,7 +59,7 @@ A sample request:
       ]
     },
     {
-      "variableName": "Variable_2",
+      "variable": "Variable_2",
       "timestamps": [
         "2021-01-01T00:00:00Z",
         "2021-01-01T00:01:00Z",
@@ -74,7 +74,7 @@ A sample request:
       ]
     },
     {
-      "variableName": "Variable_3",
+      "variable": "Variable_3",
       "timestamps": [
         "2021-01-01T00:00:00Z",
         "2021-01-01T00:01:00Z",

articles/communication-services/quickstarts/voice-video-calling/includes/call-automation/callflow-for-customer-interactions-csharp.md

@@ -5,7 +5,7 @@ services: azure-communication-services
 author: ashwinder
 
 ms.service: azure-communication-services
-ms.subservice: azure-communication-services
+ms.subservice: call-automation
 ms.date: 09/06/2022
 ms.topic: include
 ms.custom: include file
@@ -15,14 +15,9 @@ ms.author: askaur
 ## Prerequisites
 
 - An Azure account with an active subscription.
-- A deployed Communication Service resource.
-- [Acquire a PSTN phone number from the Communication Service resource](../../../telephony/get-phone-number.md?pivots=programming-language-csharp).
-- The latest [.NET library](https://dotnet.microsoft.com/download/dotnet-core) for your operating system.
-- A [web service application](https://dotnet.microsoft.com/download/dotnet-core) to handle web hook callback events.
-- Optional: [NGROK application](https://ngrok.com/) to proxy HTTP/S requests to a local development machine.
-- The [ARMClient application](https://github.com/projectkudu/ARMClient), used to configure the Event Grid subscription.
-- Obtain the NuGet package from the [Azure SDK Dev Feed](https://github.com/Azure/azure-sdk-for-net/blob/main/CONTRIBUTING.md#nuget-package-dev-feed)
-- [An Event Grid subscription for Incoming Call](../../../../how-tos/call-automation-sdk/subscribe-to-incoming-call.md)
+- A Communication Service resource.
+- [Acquire a phone number for your Communication Service resource](../../../telephony/get-phone-number.md?pivots=programming-language-csharp).
+- The latest [.NET library](https://dotnet.microsoft.com/download/dotnet-core) for your operating system. .NET 6.0 or higher is recommended as this quickstart uses the minimal API feature. 
 
 ## Create a new C# application
 
@@ -32,34 +27,48 @@ In the console window of your operating system, use the `dotnet` command to crea
     dotnet new web -n MyApplication
 ```
 
-## Install the NuGet package
+## Configure NuGet package manager
 
-During the preview phase, the NuGet package can be obtained by configuring your package manager to use the Azure SDK Dev Feed from [here](https://github.com/Azure/azure-sdk-for-net/blob/main/CONTRIBUTING.md#nuget-package-dev-feed)
+During the preview phase, the `Azure.Communication.CallAutomation` NuGet package can be obtained by configuring your package manager to use the Azure SDK Dev Feed from [here](https://github.com/Azure/azure-sdk-for-net/blob/main/CONTRIBUTING.md#nuget-package-dev-feed)
 
-## Obtain your connection string
+## Install required NuGet packages
 
-From the Azure portal, locate your Communication Service resource and click on the Keys section to obtain your connection string.
+Install the following NuGet packages to your project using the `dotnot add <package>` command. 
 
+*Azure.Communication.CallAutomation* - [Package details](https://dev.azure.com/azure-sdk/public/_artifacts/feed/azure-sdk-for-net/NuGet/Azure.Communication.CallAutomation/versions/)
+
+*Azure.Messaging.EventGrid* - [Package details](https://dev.azure.com/azure-sdk/public/_artifacts/feed/azure-sdk-for-net/NuGet/Azure.Messaging.EventGrid/versions/)
+
+## Obtain your connection string and phone number
+
+From the Azure portal, locate your Communication Service resource.
+
+1. Select on the Keys section to obtain your connection string.
 :::image type="content" source="./../../media/call-automation/Key.png" alt-text="Screenshot of Communication Services resource page on portal to access keys":::
+2. Then select on the Phone numbers section to obtain your ACS phone number.
 
-## Configure Program.cs to answer the call
+## Update Program.cs
 
 Using the minimal API feature in .NET 6, we can easily add an HTTP POST map and answer the call. A callback URI is required so the service knows how to contact your web server for subsequent calls state events such as `CallConnected` and `PlayCompleted`.  
 
-NOTE: The code sample also illustrates how you can control the callback URI by setting your own context/ID when you answer the call. All events generated by the call will be sent to the specific route you provide when answering an inbound call and the same applies to when you place an outbound call.
+In this code snippet, /api/incomingCall is the default route that will be used to listen for and answer incoming calls. At a later step, you'll register this url with Event Grid. Since Event Grid requires you to prove ownership of your Webhook endpoint before it starts delivering events to that endpoint, the code sample also handles this one time validation by processing SubscriptionValidationEvent. This requirement prevents a malicious user from flooding your endpoint with events. For more information, see this [guide](../../../../../event-grid/webhook-event-delivery.md).  
+
+The code sample also illustrates how you can control the callback URI by setting your own context/ID when you answer the call. All events generated by the call will be sent to the specific route you provide when answering an inbound call and the same applies to when you place an outbound call.  
+
 ``` csharp
 using Azure.Communication;
 using Azure.Communication.CallAutomation;
 using Azure.Messaging;
 using Azure.Messaging.EventGrid;
 using Azure.Messaging.EventGrid.SystemEvents;
 using Microsoft.AspNetCore.Mvc;
+using System.ComponentModel.DataAnnotations;
 using System.Text.Json.Nodes;
 
 var builder = WebApplication.CreateBuilder(args);
 
-var client = new CallAutomationClient(builder.Configuration["ACS:ConnectionString"]);
-var callbackUriBase = "<YOUR_NGROK_FQDN>"; // i.e. https://someguid.ngrok.io
+var client = new CallAutomationClient(builder.Configuration["ConnectionString"]);
+var callbackUriBase = builder.Configuration["callbackUriBase"]; // i.e. https://someguid.ngrok.io
 
 var app = builder.Build();
 app.MapPost("/api/incomingCall", async (
@@ -70,7 +79,7 @@ app.MapPost("/api/incomingCall", async (
         // Handle system events
         if (eventGridEvent.TryGetSystemEventData(out object eventData))
         {
-            // Handle the subscription validation event
+            // Handle the subscription validation event.
             if (eventData is SubscriptionValidationEventData subscriptionValidationEventData)
             {
                 var responseData = new SubscriptionValidationResponse
@@ -81,16 +90,19 @@ app.MapPost("/api/incomingCall", async (
             }
         }
         var jsonObject = JsonNode.Parse(eventGridEvent.Data).AsObject();
+        var callerId = (string)(jsonObject["from"]["rawId"]);
         var incomingCallContext = (string)jsonObject["incomingCallContext"];
-        var callbackUri = new Uri(callbackUriBase + $"/api/calls/{Guid.NewGuid()}");
+        var callbackUri = new Uri(callbackUriBase + $"/api/calls/{Guid.NewGuid()}?callerId={callerId}");
+
         AnswerCallResult answerCallResult = await client.AnswerCallAsync(incomingCallContext, callbackUri);
     }
     return Results.Ok();
 });
 
 app.MapPost("/api/calls/{contextId}", async (
     [FromBody] CloudEvent[] cloudEvents,
-    [FromRoute] string contextId) =>
+    [FromRoute] string contextId,
+    [Required] string callerId) =>
 {
     foreach (var cloudEvent in cloudEvents)
     {
@@ -99,12 +111,12 @@ app.MapPost("/api/calls/{contextId}", async (
         {
             // play audio then recognize 3-digit DTMF input with pound (#) stop tone
             var recognizeOptions =
-                new CallMediaRecognizeDtmfOptions(new PhoneNumberIdentifier("<Target-Participant-Phone-Number>"), 3)
+                new CallMediaRecognizeDtmfOptions(CommunicationIdentifier.FromRawId(callerId), 3)
                 {
                     InterruptPrompt = true,
                     InterToneTimeout = TimeSpan.FromSeconds(10),
                     InitialSilenceTimeout = TimeSpan.FromSeconds(5),
-                    Prompt = new FileSource(new Uri("<INSERT_AUDIO_FILE_URI>")),
+                    Prompt = new FileSource(new Uri(builder.Configuration["MediaSource"])),
                     StopTones = new[] { DtmfTone.Pound },
                     OperationContext = "MainMenu"
                 };
@@ -119,12 +131,51 @@ app.MapPost("/api/calls/{contextId}", async (
                 .AddParticipantsAsync(new AddParticipantsOptions(
                     new List<CommunicationIdentifier>()
                     {
-                        new CommunicationUserIdentifier("<ACS_ID>")
-                    }));
+                        new CommunicationUserIdentifier(builder.Configuration["ParticipantToAdd"])
+                    })
+                );
         }
     }
     return Results.Ok();
 }).Produces(StatusCodes.Status200OK);
 
 app.Run();
 ```
+
+## Set up a public URI for the local application 
+
+In this quick-start, you'll use [Ngrok tool](https://ngrok.com/) to project a public URI to the local port so that your local application can be visited by the internet. The public URI is needed to receive the Event Grid `IncomingCall` event and Call Automation events using webhooks.
+
+First, determine the port of the .NET application. Minimal API dynamically allocates a port for the project at the time of creation. Find out the http port in <PROJECT_ROOT>\Properties\launchSettings.json.
+:::image type="content" source="./../../media/call-automation/dotnet-application-port.jpg" alt-text="Screenshot of demo application's launchsetting.json file":::
+
+Then, [install Ngrok](https://ngrok.com/download) and run Ngrok with the following command: `ngrok http <port>`. This command will create a public URI like `https://ff2f-75-155-253-232.ngrok.io/`, and it is your Ngrok Fully Qualified Domain Name(Ngrok_FQDN). Keep Ngrok running while following the rest of this quick-start.
+
+## Set up environment variables
+
+In Visual Studio, right click at your project and then select "Manage User Secrets" to configure confidential environment variables.
+
+:::image type="content" source="./../../media/call-automation/dotnet-user-secret.jpg" alt-text="Screenshot of how to find out 'Manage User Secrets'":::
+
+Read more about Secret Manager at [Safe storage of app secrets in development in ASP.NET Core](https://learn.microsoft.com/aspnet/core/security/app-secrets)
+
+``` json
+{
+  ...
+    "ConnectionString": "Your_ACS_resource_connection_string",
+    "CallbackUriBase": "Your_Ngrok_FQDN",
+    "MediaSource": "Link_to_media_file_for_play_prompt",
+    "ParticipantToAdd": "The_participant_to_be_added_after_recognizing_tones"
+  ...
+}
+```
+
+ParticipantToAdd used in the code snippet is assumed to be an ACS User MRI.
+
+## Run the app
+
+Open Your_Project_Name.csproj file in your project with Visual Studio, and then select Run button or press F5 on your keyboard.
+
+## Set up IncomingCall event
+
+IncomingCall is an Azure Event Grid event for notifying incoming calls to your Communication Services resource, like the phone number purchased in pre-requisites. Follow [this guide](../../../../how-tos/call-automation-sdk/subscribe-to-incoming-call.md) to set up your IncomingCall event.