Merge pull request #224033 from MicrosoftDocs/main

Publish to live, Monday 4 AM PST, 1/16

Author: ttorble

.openpublishing.redirection.azure-productivity.json

@@ -84,6 +84,11 @@
       "source_path": "articles/lab-services/how-to-manage-vm-pool-within-canvas.md",
       "redirect_url": "/azure/lab-services/how-to-manage-labs-within-canvas",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/lab-services/how-to-enable-nested-virtualization-template-vm.md",
+      "redirect_url": "/azure/lab-services/concept-nested-virtualization-template-vm",
+      "redirect_document_id": true
     }
   ]
 }

articles/active-directory/external-identities/media/self-service-sign-up-user-flow/assign-app-to-user-flow.png

@@ -5,7 +5,7 @@ services: active-directory
 ms.service: active-directory
 ms.subservice: B2B
 ms.topic: how-to
-ms.date: 01/06/2023
+ms.date: 01/16/2023
 
 ms.author: mimart
 author: msmimart
@@ -52,7 +52,8 @@ Before you can add a self-service sign-up user flow to your applications, you ne
 1. Select **User settings**, and then under **External users**, select **Manage external collaboration settings**.
 1. Set the **Enable guest self-service sign up via user flows** toggle to **Yes**.
 
-   ![Enable guest self-service sign-up](media/self-service-sign-up-user-flow/enable-self-service-sign-up.png)
+   :::image type="content" source="media/self-service-sign-up-user-flow/enable-self-service-sign-up.png" alt-text="Screenshot of the enable guest self-service sign up toggle.":::
+
 5. Select **Save**.
 ## Create the user flow for self-service sign-up
 
@@ -63,17 +64,17 @@ Next, you'll create the user flow for self-service sign-up and add it to an appl
 3. In the left menu, select **External Identities**.
 4. Select **User flows**, and then select **New user flow**.
 
-   ![Add a new user flow button](media/self-service-sign-up-user-flow/new-user-flow.png)
+   :::image type="content" source="media/self-service-sign-up-user-flow/new-user-flow.png" alt-text="Screenshot of the new user flow button.":::
 
 5. Select the user flow type (for example, **Sign up and sign in**), and then select the version (**Recommended** or **Preview**).
-6. On the **Create** page, enter a **Name** for the user flow. Note that the name is automatically prefixed with **B2X_1_**.
+6. On the **Create** page, enter a **Name** for the user flow. The name is automatically prefixed with **B2X_1_**.
 7. In the **Identity providers** list, select one or more identity providers that your external users can use to log into your application. **Azure Active Directory Sign up** is selected by default. (See [Before you begin](#before-you-begin) earlier in this article to learn how to add identity providers.)
-8. Under **User attributes**, choose the attributes you want to collect from the user. For additional attributes, select **Show more**. For example, select **Show more**, and then choose attributes and claims for **Country/Region**, **Display Name**, and **Postal Code**. Select **OK**.
+8. Under **User attributes**, choose the attributes you want to collect from the user. For more attributes, select **Show more**. For example, select **Show more**, and then choose attributes and claims for **Country/Region**, **Display Name**, and **Postal Code**. Select **OK**.
 
-   ![Create a new user flow page](media/self-service-sign-up-user-flow/create-user-flow.png)
+   :::image type="content" source="media/self-service-sign-up-user-flow/create-user-flow.png" alt-text="Screenshot of the new user flow creation page. ":::
 
-> [!NOTE]
-> You can only collect attributes when a user signs up for the first time. After a user signs up, they will no longer be prompted to collect attribute information, even if you change the user flow.
+   > [!NOTE]
+   > You can only collect attributes when a user signs up for the first time. After a user signs up, they will no longer be prompted to collect attribute information, even if you change the user flow.
 
 8. Select **Create**.
 9. The new user flow appears in the **User flows** list. If necessary, refresh the page.
@@ -86,7 +87,7 @@ You can choose order in which the attributes are displayed on the sign-up page.
 2. Select **External Identities**, select **User flows**.
 3. Select the self-service sign-up user flow from the list.
 4. Under **Customize**, select **Page layouts**.
-5. The attributes you chose to collect are listed. To change the order of display, select an attribute, and then select **Move up**, **Move down**, **Move to the top**, or **Move to the bottom**.
+5. The attributes you chose to collect are listed. To change the order of display, select an attribute, and then select **Move up**, **Move down**, **Move to top**, or **Move to bottom**.
 6. Select **Save**.
 
 ## Add applications to the self-service sign-up user flow
@@ -101,7 +102,7 @@ Now you'll associate applications with the user flow to enable sign-up for those
 6. In the left menu, under **Use**, select **Applications**.
 7. Select **Add application**.
 
-   ![Assign an application to the user flow](media/self-service-sign-up-user-flow/assign-app-to-user-flow.png)
+   :::image type="content" source="media/self-service-sign-up-user-flow/assign-app-to-user-flow.png" alt-text="Screenshot of adding an application to the user flow.":::
 
 8. Select the application from the list. Or use the search box to find the application, and then select it.
 9. Click **Select**.
@@ -112,4 +113,3 @@ Now you'll associate applications with the user flow to enable sign-up for those
 - [Add Facebook to your list of social identity providers](facebook-federation.md)
 - [Use API connectors to customize and extend your user flows via web APIs](api-connectors-overview.md)
 - [Add custom approval workflow to your user flow](self-service-sign-up-add-approvals.md)
-- [Learn more about initiating an OAuth 2.0 authorization code flow](../develop/v2-oauth2-auth-code-flow.md#request-an-authorization-code)

articles/active-directory/external-identities/media/self-service-sign-up-user-flow/create-user-flow.png

@@ -11,7 +11,7 @@ ms.custom: devx-track-azurepowershell, engagement-fy23
 # Start/Stop VMs during off-hours overview
 
 > [!NOTE]
-> Start/Stop VM during off-hours, version 1 is going to retire soon by CY23 and is unavailable in the marketplace now. We recommend that you start using [version 2](/articles/azure-functions/start-stop-vms/overview.md), which is now generally available. The new version offers all existing capabilities and provides new features, such as multi-subscription support from a single Start/Stop instance. If you have the version 1 solution already deployed, you can still use the feature, and we will provide support until retirement in CY23. The details on announcement will be shared soon.
+> Start/Stop VM during off-hours, version 1 is going to retire soon by CY23 and is unavailable in the marketplace now. We recommend that you start using [version 2](https://learn.microsoft.com/azure/azure-functions/start-stop-vms/overview), which is now generally available. The new version offers all existing capabilities and provides new features, such as multi-subscription support from a single Start/Stop instance. If you have the version 1 solution already deployed, you can still use the feature, and we will provide support until retirement in CY23. The details on announcement will be shared soon.
 
 The Start/Stop VMs during off-hours feature start or stops enabled Azure VMs. It starts or stops machines on user-defined schedules, provides insights through Azure Monitor logs, and sends optional emails by using [action groups](../azure-monitor/alerts/action-groups.md). The feature can be enabled on both Azure Resource Manager and classic VMs for most scenarios.
 

articles/active-directory/external-identities/media/self-service-sign-up-user-flow/enable-self-service-sign-up.png

@@ -28,7 +28,6 @@ The following providers and their corresponding Kubernetes distributions have su
 | Canonical    | [Charmed Kubernetes](https://ubuntu.com/kubernetes) | [1.24](https://ubuntu.com/kubernetes/docs/1.24/components) |
 | SUSE Rancher      | [Rancher Kubernetes Engine](https://rancher.com/products/rke/) | RKE CLI version: [v1.3.13](https://github.com/rancher/rke/releases/tag/v1.3.13); Kubernetes versions: 1.24.2, 1.23.8  |
 | Nutanix      | [Nutanix Kubernetes Engine](https://www.nutanix.com/products/kubernetes-engine)    | Version [2.5](https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Engine-v2_5:Nutanix-Kubernetes-Engine-v2_5); upstream K8s v1.23.11 |
-| Platform9      | [Platform9 Managed Kubernetes (PMK)](https://platform9.com/managed-kubernetes/)    | PMK Version [5.3.0](https://platform9.com/docs/kubernetes/release-notes#platform9-managed-kubernetes-version-53-release-notes); Kubernetes versions: v1.20.5, v1.19.6, v1.18.10 |
 | Kublr	| [Kublr Managed K8s](https://kublr.com/managed-kubernetes/) Distribution | Upstream K8s Version: 1.22.10 <br> Upstream K8s Version: 1.21.3 |
 | Mirantis | [Mirantis Kubernetes Engine](https://www.mirantis.com/software/mirantis-kubernetes-engine/) | MKE Version [3.6.0](https://docs.mirantis.com/mke/3.6/release-notes/3-6-0.html) <br> MKE Version [3.5.5](https://docs.mirantis.com/mke/3.5/release-notes/3-5-5.html) <br> MKE Version [3.4.7](https://docs.mirantis.com/mke/3.4/release-notes/3-4-7.html) |
 | Wind River | [Wind River Cloud Platform](https://www.windriver.com/studio/operator/cloud-platform) | Wind River Cloud Platform 22.06; Upstream K8s version: 1.23.1 <br>Wind River Cloud Platform 21.12; Upstream K8s version: 1.21.8 <br>Wind River Cloud Platform 21.05; Upstream K8s version: 1.18.1 |

articles/active-directory/external-identities/media/self-service-sign-up-user-flow/new-user-flow.png

@@ -1,10 +1,12 @@
 ---
 title: Azure Functions SignalR Service input binding
 description: Learn to return a SignalR service endpoint URL and access token in Azure Functions.
+author: Y-Sindo
 ms.topic: reference
 ms.devlang: csharp, java, javascript, python
 ms.custom: devx-track-csharp
-ms.date: 03/04/2022
+ms.date: 01/13/2022
+ms.author: zityang
 zone_pivot_groups: programming-languages-set-functions-lang-workers
 ---
 
@@ -38,13 +40,9 @@ public static SignalRConnectionInfo Negotiate(
 
 # [Isolated process](#tab/isolated-process)
 
-The following example shows a SignalR trigger that reads a message string from one hub using a SignalR trigger and writes it to a second hub using an output binding. The data required to connect to the output binding is obtained as a `MyConnectionInfo` object from an input binding defined using a `SignalRConnectionInfo` attribute. 
+The following example shows a SignalR trigger that reads a message string from one hub using a SignalR trigger and writes it to a second hub using an output binding. The data required to connect to the output binding is obtained as a `MyConnectionInfo` object from an input binding defined using a `SignalRConnectionInfo` attribute.
 
-:::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/SignalR/SignalRFunction.cs" range="12-31":::
-
-The `MyConnectionInfo` and `MyMessage` classes are defined as follows:
-
-:::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/SignalR/SignalRFunction.cs" range="34-46":::
+:::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/SignalR/SignalRNegotiationFunctions.cs" id="snippet_negotiate":::
 
 # [C# Script](#tab/csharp-script)
 
@@ -77,8 +75,8 @@ public static SignalRConnectionInfo Run(HttpRequest req, SignalRConnectionInfo c
 ```
 
 ---
-::: zone-end  
-::: zone pivot="programming-language-javascript,programming-language-python,programming-language-powershell"  
+::: zone-end
+::: zone pivot="programming-language-javascript,programming-language-python,programming-language-powershell"
 
 The following example shows a SignalR connection info input binding in a *function.json* file and a function that uses the binding to return the connection information.
 
@@ -105,12 +103,12 @@ module.exports = async function (context, req, connectionInfo) {
 };
 ```
 
-::: zone-end  
-::: zone pivot="programming-language-powershell" 
- 
+::: zone-end
+::: zone pivot="programming-language-powershell"
+
 Complete PowerShell examples are pending.
-::: zone-end 
-::: zone pivot="programming-language-python"  
+::: zone-end
+::: zone pivot="programming-language-python"
 
 The following example shows a SignalR connection info input binding in a *function.json* file and a [Python function](functions-reference-python.md) that uses the binding to return the connection information.
 
@@ -127,7 +125,7 @@ def main(req: func.HttpRequest, connectionInfoJson: str) -> func.HttpResponse:
     )
 ```
 
-::: zone-end 
+::: zone-end
 ::: zone pivot="programming-language-java"
 
 The following example shows a [Java function](functions-reference-java.md) that acquires SignalR connection information using the input binding and returns it over HTTP.
@@ -146,7 +144,7 @@ public SignalRConnectionInfo negotiate(
 }
 ```
 
-:::zone-end  
+:::zone-end
 
 ## Usage
 
@@ -165,7 +163,7 @@ You can set the `UserId` property of the binding to the value from either header
 ```cs
 [FunctionName("negotiate")]
 public static SignalRConnectionInfo Negotiate(
-    [HttpTrigger(AuthorizationLevel.Anonymous)]HttpRequest req, 
+    [HttpTrigger(AuthorizationLevel.Anonymous)]HttpRequest req,
     [SignalRConnectionInfo
         (HubName = "chat", UserId = "{headers.x-ms-client-principal-id}")]
         SignalRConnectionInfo connectionInfo)
@@ -177,7 +175,15 @@ public static SignalRConnectionInfo Negotiate(
 
 # [Isolated process](#tab/isolated-process)
 
-Sample code not available for the isolated worker process. 
+```cs
+[Function("Negotiate")]
+public static string Negotiate([HttpTrigger(AuthorizationLevel.Anonymous)] HttpRequestData req,
+    [SignalRConnectionInfoInput(HubName = "serverless", UserId = "{headers.x-ms-client-principal-id}")] string connectionInfo)
+{
+    // The serialization of the connection info object is done by the framework. It should be camel case. The SignalR client respects the camel case response only.
+    return connectionInfo;
+}
+```
 
 # [C# Script](#tab/csharp-script)
 
@@ -214,10 +220,21 @@ public static SignalRConnectionInfo Run(HttpRequest req, SignalRConnectionInfo c
 ::: zone-end
 
 ::: zone pivot="programming-language-java"
-SignalR trigger isn't currently supported for Java. 
-::: zone-end 
- 
-::: zone pivot="programming-language-javascript,programming-language-python,programming-language-powershell"  
+```java
+@FunctionName("negotiate")
+public SignalRConnectionInfo negotiate(
+        @HttpTrigger(
+            name = "req",
+            methods = { HttpMethod.POST, HttpMethod.GET },
+            authLevel = AuthorizationLevel.ANONYMOUS)
+            HttpRequestMessage<Optional<String>> req,
+        @SignalRConnectionInfoInput(name = "connectionInfo", hubName = "simplechat", userId = "{headers.x-ms-signalr-userid}") SignalRConnectionInfo connectionInfo) {
+    return connectionInfo;
+}
+```
+::: zone-end
+
+::: zone pivot="programming-language-javascript,programming-language-python,programming-language-powershell"
 
 You can set the `userId` property of the binding to the value from either header using a [binding expression](./functions-bindings-expressions-patterns.md): `{headers.x-ms-client-principal-id}` or `{headers.x-ms-client-principal-name}`.
 
@@ -235,7 +252,7 @@ Here's binding data in the *function.json* file:
 ```
 
 ::: zone-end
-::: zone pivot="programming-language-javascript"  
+::: zone pivot="programming-language-javascript"
 Here's the JavaScript code:
 
 ```javascript
@@ -246,12 +263,12 @@ module.exports = async function (context, req, connectionInfo) {
 };
 ```
 
-::: zone-end  
-::: zone pivot="programming-language-powershell" 
- 
+::: zone-end
+::: zone pivot="programming-language-powershell"
+
 Complete PowerShell examples are pending.
-::: zone-end 
-::: zone pivot="programming-language-python"  
+::: zone-end
+::: zone pivot="programming-language-python"
 
 Here's the Python code:
 
@@ -268,7 +285,7 @@ def main(req: func.HttpRequest, connectionInfo: str) -> func.HttpResponse:
     )
 ```
 
-::: zone-end 
+::: zone-end
 ::: zone pivot="programming-language-java"
 
 You can set the `userId` property of the binding to the value from either header using a [binding expression](./functions-bindings-expressions-patterns.md): `{headers.x-ms-client-principal-id}` or `{headers.x-ms-client-principal-name}`.
@@ -330,9 +347,9 @@ The following table explains the binding configuration properties that you set i
 
 ---
 
-::: zone-end 
-::: zone pivot="programming-language-java" 
- 
+::: zone-end
+::: zone pivot="programming-language-java"
+
 ## Annotations
 
 The following table explains the supported settings for the `SignalRConnectionInfoInput` annotation.
@@ -344,8 +361,8 @@ The following table explains the supported settings for the `SignalRConnectionIn
 |**userId**| Optional: The value of the user identifier claim to be set in the access key token. |
 |**connectionStringSetting**| The name of the app setting that contains the SignalR Service connection string, which defaults to `AzureSignalRConnectionString`. |
 
-::: zone-end  
-::: zone pivot="programming-language-javascript,programming-language-powershell,programming-language-python" 
+::: zone-end
+::: zone pivot="programming-language-javascript,programming-language-powershell,programming-language-python"
 ## Configuration
 
 The following table explains the binding configuration properties that you set in the *function.json* file.
@@ -364,4 +381,4 @@ The following table explains the binding configuration properties that you set i
 ## Next steps
 
 - [Handle messages from SignalR Service  (Trigger binding)](./functions-bindings-signalr-service-trigger.md)
-- [Send SignalR Service messages  (Output binding)](./functions-bindings-signalr-service-output.md) 
+- [Send SignalR Service messages  (Output binding)](./functions-bindings-signalr-service-output.md)

articles/active-directory/external-identities/self-service-sign-up-user-flow.md

@@ -1,10 +1,12 @@
 ---
 title: Azure Functions SignalR Service output binding
 description: Learn about the SignalR Service output binding for Azure Functions.
+author: Y-Sindo
 ms.topic: reference
 ms.devlang: csharp, java, javascript, python
 ms.custom: devx-track-csharp
-ms.date: 03/04/2022
+ms.date: 01/13/2023
+ms.author: zityang
 zone_pivot_groups: programming-languages-set-functions-lang-workers
 ---
 
@@ -50,7 +52,7 @@ public static Task SendMessage(
 
 The following example shows a function that sends a message using the output binding to all connected clients. The *newMessage* is the name of the method to be invoked on each client.
 
-:::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/SignalR/SignalROutputBindingFunctions.cs" range="13-24":::
+:::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/SignalR/SignalROutputBindingFunctions2.cs" id="snippet_broadcast_to_all":::
 
 # [C# Script](#tab/csharp-script)
 
@@ -189,7 +191,7 @@ public static Task SendMessage(
 
 # [Isolated process](#tab/isolated-process)
 
-:::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/SignalR/SignalROutputBindingFunctions.cs" range="39-50":::
+:::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/SignalR/SignalROutputBindingFunctions2.cs" id="snippet_send_to_user":::
 
 # [C# Script](#tab/csharp-script)
 
@@ -331,7 +333,7 @@ public static Task SendMessage(
 ```
 # [Isolated process](#tab/isolated-process)
 
-:::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/SignalR/SignalROutputBindingFunctions.cs" range="52-63":::
+:::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/SignalR/SignalROutputBindingFunctions2.cs" id="snippet_send_to_group":::
 
 # [C# Script](#tab/csharp-script)
 
@@ -478,9 +480,9 @@ public static Task AddToGroup(
 
 # [Isolated process](#tab/isolated-process)
 
-Specify `SignalRGroupActionType` to add or remove a member. The following example adds a user to a group.
+Specify `SignalRGroupActionType` to add or remove a member. The following example removes a user from a group.
 
-:::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/SignalR/SignalROutputBindingFunctions.cs" range="80-89":::
+:::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/SignalR/SignalROutputBindingFunctions2.cs" id="snippet_remove_from_group":::
 
 # [C# Script](#tab/csharp-script)