Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into HubMetric

Author: siddomala

articles/azure-functions/functions-dotnet-class-library.md

@@ -31,9 +31,6 @@ Azure Functions supports C# and C# script programming languages. If you're looki
 
 ### Updating to target .NET 8
 
-> [!NOTE]
-> Targeting .NET 8 with the in-process model is not yet enabled for apps in sovereign clouds. Updates will be communicated on [this tracking thread on GitHub](https://github.com/Azure/azure-functions-host/issues/9951).
-
 Apps using the in-process model can target .NET 8 by following the steps outlined in this section. However, if you choose to exercise this option, you should still begin planning your [migration to the isolated worker model](./migrate-dotnet-to-isolated-model.md) in advance of [support ending for the in-process model on November 10, 2026](https://aka.ms/azure-functions-retirements/in-process-model).
 
 Many apps can change the configuration of the function app in Azure without updates to code or redeployment. To run .NET 8 with the in-process model, three configurations are required:

articles/azure-government/documentation-government-overview-dod.md

@@ -7,7 +7,7 @@ ms.service: azure-government
 ms.topic: article
 ms.custom: references_regions
 recommendations: false
-ms.date: 05/09/2023
+ms.date: 08/15/2024
 ---
 
 # Department of Defense (DoD) in Azure Government
@@ -92,7 +92,7 @@ The following services are in scope for DoD IL5 PA in US DoD regions (US DoD Cen
 - [Microsoft Stream](/stream/overview)
 - [Network Watcher](https://azure.microsoft.com/services/network-watcher/)
 - [Power Apps](/powerapps/powerapps-overview)
-- [Power Apps portal](https://powerapps.microsoft.com/portals/)
+- [Power Pages](https://powerapps.microsoft.com/portals/)
 - [Power Automate](/power-automate/getting-started) (formerly Microsoft Flow)
 - [Power BI](https://powerbi.microsoft.com/)
 - [Power BI Embedded](https://azure.microsoft.com/services/power-bi-embedded/)

articles/education-hub/create-assignment-allocate-credit.md

@@ -1,21 +1,20 @@
 ---
-title: Create an assignment and allocate credit in the Azure Education Hub
+title: Create a lab and allocate credit in the Azure Education Hub
 description: Learn how to create an assignment, allocate credit, and invite students to a course in the Azure Education Hub.
 author: rymend
 ms.author: rymend
 ms.topic: overview
-ms.date: 06/30/2020
+ms.date: 08/14/2024
 ms.service: azure-education
 ---
 
-# Create an assignment and allocate credit in the Azure Education Hub
+# Create a lab and allocate credit in the Azure Education Hub
 
-After you set up a course in the Azure Education Hub, you can create an assignment where you allocate credit and invite selected students to your course.
+After you set up a lab in the Azure Education Hub, you can add students and allocate credits to them to deploy resources.
 
 ## Prerequisites
 
 - An academic grant with an approved credit amount
-- A course created in the Education Hub
 - A work or school account and a subscription within the course that will access your Azure credit
 
 ### Accounts
@@ -27,17 +26,15 @@ The Education Hub accepts any email address in the standard format. It does *not
 
 When you add a work or school account (for example, *student*@*school*.edu) by using role-based access control (RBAC) in the Educator Sponsor Portal or the [Azure portal](https://portal.azure.com), Azure automatically sends email to the recipient. This email requires the user to accept the new account and Azure role before receiving access to the subscription.
 
-If you're a teaching assistant or a professor for a course, be sure to inform students of this requirement so that their subscription appears in the Azure portal as expected. The email should look similar to this example:
+If you're a teaching assistant or a professor for a course, be sure to inform students of this requirement so that their subscription appears in the Azure portal as expected.
 
-:::image type="content" source="media/create-assignment-allocate-credit/azure-active-directory-get-started.png" alt-text="Screenshot of an email invitation to access applications in an organization." border="false":::
+## Create a lab and invite students
 
-## Create an assignment and invite students to the course
+1. Create a lab and fill in the required information such as lab name and method to invite students.
 
-1. Choose the amount of funds to credit to the student's subscription. If not all students will receive the same amount, you can select **Change** and apply a custom amount to each student or project group.
-
-1. Select **Create assignment**.
-1. Optionally, you can remove existing students by selecting **Remove** next to each student's name.
-1. When you finish, select the **Close** button. The additional permissions appear on the **Sponsor Credit Management** page.
+2. After you create the lab, you can begin inviting students to the lab
+3. Optionally, you can remove existing students by selecting **Remove** next to each student's name.
+4. When you finish, the students added will receive an invitation to join the lab.
 
 ## Related content
 

articles/education-hub/index.yml

@@ -10,7 +10,7 @@ metadata:
   ms.topic: landing-page
   author: tfosmark 
   ms.author: rymend 
-  ms.date: 07/14/2020 
+  ms.date: 08/15/2024 
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | whats-new
 
@@ -22,12 +22,14 @@ landingContent:
         links:
           - text: What is Azure Dev Tools for Teaching?
             url: ./azure-dev-tools-teaching/about-program.md
-      - linkListType: how-to-guide
+      - linkListType: quickstart
         links:
           - text: Enroll in Azure Dev Tools for Teaching
             url: ./azure-dev-tools-teaching/enroll-renew-subscription.md
           - text: Set up access
             url: ./azure-dev-tools-teaching/set-up-access.md
+      - linkListType: how-to-guide
+        links:
           - text: Manage students
             url: ./azure-dev-tools-teaching/manage-students.md
           - text: Download software
@@ -57,5 +59,11 @@ landingContent:
     linkLists:
       - linkListType: how-to-guide
         links:
+          - text: Get started with the Azure Education Hub
+            url: get-started-education-hub.md
+      - linkListType: how-to-guide
+        links:
+          - text: Manage your academic grant
+            url: hub-overview-page.md
           - text: Find IDs
             url: find-ids.md

articles/healthcare-apis/deidentification/manage-access-rbac.md

@@ -11,13 +11,11 @@ ms.date: 07/16/2024
 
 # Use Azure role-based access control with the de-identification service (preview)
 
-Microsoft Entra ID authorizes access rights to secured resources through Azure role-based access control (RBAC). The de-identification service (preview) defines a set of
-built-in roles that encompass common sets of permissions used to access de-identification functionality.
+Microsoft Entra ID authorizes access rights to secured resources through Azure role-based access control (RBAC). The de-identification service (preview) defines a set of built-in roles that encompass common sets of permissions used to access de-identification functionality.
 
 Microsoft Entra ID uses the concept of a security principal, which can be a user, a group, an application service principal, or a [managed identity for Azure resources](/entra/identity/managed-identities-azure-resources/overview).
 
-When an Azure role is assigned to a Microsoft Entra ID security principal over a specific scope, Azure grants access to that scope for that security principal. For more information about scopes, see
-[Understand scope for Azure RBAC](/azure/role-based-access-control/scope-overview).
+When an Azure role is assigned to a Microsoft Entra ID security principal over a specific scope, Azure grants access to that scope for that security principal. For more information about scopes, see [Understand scope for Azure RBAC](/azure/role-based-access-control/scope-overview).
 
 ## Prerequisites
 
@@ -47,8 +45,7 @@ You can use different tools to assign built-in roles.
 
 # [Azure portal](#tab/azure-portal)
 
-To use the de-identification service (preview), with Microsoft Entra ID credentials, a security principal must be assigned one of the built-in roles. To learn how to assign these roles to a security
-principal, follow the steps in [Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal).
+To use the de-identification service (preview), with Microsoft Entra ID credentials, a security principal must be assigned one of the built-in roles. To learn how to assign these roles to a security principal, follow the steps in [Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal).
 
 # [Azure PowerShell](#tab/azure-powershell)
 
@@ -89,15 +86,13 @@ For more information, see [Assign Azure roles using Azure PowerShell](/azure/rol
 
 # [Azure CLI](#tab/azure-pcli)
 
-To assign an Azure role to a security principal with Azure CLI, use the [az role assignment create](/cli/azure/role/assignment) command. In order to run the command, you must have a role that includes
-**Microsoft.Authorization/roleAssignments/write** permissions assigned to you at the corresponding scope or higher.
+To assign an Azure role to a security principal with Azure CLI, use the [az role assignment create](/cli/azure/role/assignment) command. In order to run the command, you must have a role that includes **Microsoft.Authorization/roleAssignments/write** permissions assigned to you at the corresponding scope or higher.
 
 The format of the command can differ based on the type of security principal, but `role` and `scope` are required parameters.
 
 The scope for a de-identification service (preview) is in the form `/subscriptions/<Subscription ID>/resourceGroups/<Resource Group Name>/providers/Microsoft.HealthDataAIServices/deidServices/<Deidentification Service Name>`
 
-The following example assigns the **DeID Data Owner** built-in role to a user, scoped to a specific de-identification service. Make sure to replace the placeholder values 
-in angle brackets `<>` with your own values:
+The following example assigns the **DeID Data Owner** built-in role to a user, scoped to a specific de-identification service. Make sure to replace the placeholder values in angle brackets `<>` with your own values:
 
 ```azurecli
 az role assignment create \

articles/vpn-gateway/about-gateway-skus.md

@@ -4,7 +4,7 @@ description: Learn about VPN Gateway SKUs.
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: conceptual
-ms.date: 07/23/2024
+ms.date: 08/15/2024
 ms.author: cherylmc 
 
 ---
@@ -46,29 +46,28 @@ When you configure a virtual network gateway SKU, select the SKU that satisfies
 | ---    | ---         |
 |**Basic** (**)   | **Route-based VPN**: 10 tunnels for S2S/connections; no RADIUS authentication for P2S; no IKEv2 for P2S<br>**Policy-based VPN**: (IKEv1): 1 S2S/connection tunnel; no P2S|
 | **All Generation1 and Generation2 SKUs except Basic** | **Route-based VPN**: up to 100 tunnels (*), P2S, BGP, active-active, custom IPsec/IKE policy, ExpressRoute/VPN coexistence |
-|        |             |
 
 (*) You can configure "PolicyBasedTrafficSelectors" to connect a route-based VPN gateway to multiple on-premises policy-based firewall devices. Refer to [Connect VPN gateways to multiple on-premises policy-based VPN devices using PowerShell](vpn-gateway-connect-multiple-policybased-rm-ps.md) for details.
 
-(\*\*) The Basic SKU has certain feature and performance limitations and should not be used for production purposes. Verify that the feature that you need is supported before you use the Basic SKU. The Basic SKU doesn't support IPv6 and can only be configured using PowerShell or Azure CLI. Additionally, the Basic SKU doesn't support RADIUS authentication.
+(\*\*) The Basic SKU has certain feature and performance limitations and shouldn't be used for production purposes. Verify that the feature that you need is supported before you use the Basic SKU. The Basic SKU doesn't support IPv6 and can only be configured using PowerShell or Azure CLI. Additionally, the Basic SKU doesn't support RADIUS authentication.
 
 ## <a name="workloads"></a>Gateway SKUs - Production vs. Dev-Test workloads
 
 Due to the differences in SLAs and feature sets, we recommend the following SKUs for production vs. dev-test:
 
-| **Workload**                       | **SKUs**               |
-| ---                                | ---                    |
+| **Workload**     | **SKUs**       |
+| ---         | ---             |
 | **Production, critical workloads** | All Generation1 and Generation2 SKUs, except Basic|
 | **Dev-test or proof of concept**   | Basic (**)             |
-|                                    |                        |
 
-(\*\*) The Basic SKU has certain feature and performance limitations and should not be used for production purposes. Verify that the feature that you need is supported before you use the Basic SKU. The Basic SKU doesn't support IPv6 and can only be configured using PowerShell or Azure CLI. Additionally, the Basic SKU doesn't support RADIUS authentication.
+
+(\*\*) The Basic SKU has certain feature and performance limitations and shouldn't be used for production purposes. Verify that the feature that you need is supported before you use the Basic SKU. The Basic SKU doesn't support IPv6 and can only be configured using PowerShell or Azure CLI. Additionally, the Basic SKU doesn't support RADIUS authentication.
 
 If you're using the old SKUs (legacy), the production SKU recommendations are Standard and HighPerformance. For information and instructions for old SKUs, see [Gateway SKUs (legacy)](vpn-gateway-about-skus-legacy.md).
 
 ## About legacy SKUs
 
-For information about working with the legacy gateway SKUs (Basic, Standard, and High Performance), including SKU deprecation, see [Managing legacy gateway SKUs](vpn-gateway-about-skus-legacy.md).
+For information about working with the legacy gateway SKUs (Standard and High Performance), including SKU deprecation, see [Managing legacy gateway SKUs](vpn-gateway-about-skus-legacy.md).
 
 ## Specify a SKU
 

articles/vpn-gateway/vpn-gateway-about-skus-legacy.md

@@ -21,7 +21,24 @@ For SKU deprecation, see the [SKU deprecation](#sku-deprecation) and SKU depreca
 
 ## <a name="agg"></a>Estimated aggregate throughput by SKU
 
-[!INCLUDE [Aggregated throughput by legacy SKU](../../includes/vpn-gateway-table-gwtype-legacy-aggtput-include.md)]
+The following table shows the gateway types and the estimated aggregate throughput by gateway SKU. This table applies to the Resource Manager and classic deployment models.
+
+Pricing differs between gateway SKUs. For more information, see [VPN Gateway Pricing](https://azure.microsoft.com/pricing/details/vpn-gateway).
+
+The UltraPerformance gateway SKU isn't represented in this table. For information about the UltraPerformance SKU, see the [ExpressRoute](../expressroute/expressroute-about-virtual-network-gateways.md) documentation.
+
+|  | **VPN Gateway throughput (1)** | **VPN Gateway max IPsec tunnels (2)** | **ExpressRoute Gateway throughput** | **VPN Gateway and ExpressRoute coexist** |
+| --- | --- | --- | --- | --- |
+| **Standard SKU (3)(4)** |100 Mbps |10 |1000 Mbps |Yes |
+| **High Performance SKU (3)** |200 Mbps |30 |2000 Mbps |Yes |
+
+(1) The VPN throughput is a rough estimate based on the measurements between VNets in the same Azure region. It isn't a guaranteed throughput for cross-premises connections across the Internet. It's the maximum possible throughput measurement.
+
+(2) The number of tunnels refer to RouteBased VPNs. A PolicyBased VPN can only support one Site-to-Site VPN tunnel.
+
+(3) PolicyBased VPNs aren't supported for this SKU. They're supported for the Basic SKU.
+
+(4) Active-active S2S VPN Gateway connections aren't supported for this SKU. Active-active is supported on the HighPerformance SKU.
 
 ## <a name="config"></a>Supported configurations by SKU and VPN type
 

includes/functions-dotnet-migrate-v4-versions.md

@@ -12,16 +12,14 @@ When you migrate your function app, you have the opportunity to choose the targe
 
 | .NET version | [.NET Official Support Policy] release type |  Functions process model<sup>1,2</sup> | 
 | --- | --- | --- |
-| .NET 8 | LTS (end of support November 10, 2026) | [Isolated worker model],<br/>[In-process model]<sup>2,3</sup>  | 
+| .NET 8 | LTS (end of support November 10, 2026) | [Isolated worker model],<br/>[In-process model]<sup>2</sup>  | 
 | .NET 6 | LTS (end of support November 12, 2024) |  [Isolated worker model],<br/>[In-process model]<sup>2</sup>  | 
 | .NET Framework 4.8 | [See policy][netfxpolicy] | [Isolated worker model] |  
 
 <sup>1</sup> The [isolated worker model] supports Long Term Support (LTS) and Standard Term Support (STS) versions of .NET, as well as .NET Framework. The [in-process model] only supports LTS releases of .NET, ending with .NET 8. For a full feature and functionality comparison between the two models, see [Differences between in-process and isolate worker process .NET Azure Functions](../articles/azure-functions/dotnet-isolated-in-process-differences.md). 
 
 <sup>2</sup> Support ends for the in-process model on November 10, 2026. For more information, see [this support announcement](https://aka.ms/azure-functions-retirements/in-process-model). For continued full support, you should  [migrate your apps to the isolated worker model](../articles/azure-functions/migrate-dotnet-to-isolated-model.md).
 
-<sup>3</sup> Targeting .NET 8 with the in-process model is not yet enabled for apps in sovereign clouds. Updates will be communicated on [this tracking thread on GitHub](https://github.com/Azure/azure-functions-host/issues/9951).
-
 <!-- <sup>2</sup> See [Preview .NET versions in the isolated worker model](../articles/azure-functions/dotnet-isolated-process-guide.md#preview-net-versions) for details on support, current restrictions, and instructions for using the preview version. -->
 
 [.NET Official Support Policy]: https://dotnet.microsoft.com/platform/support/policy

includes/functions-supported-languages.md

@@ -29,11 +29,9 @@ Your function code runs in the same process as the Functions host process. Suppo
 
 | Supported version | Support level | Expected community EOL date |
 | ---- | ---- |--- |
-| [.NET 8 (LTS)](https://dotnet.microsoft.com/platform/support/policy/dotnet-core#lifecycle)<sup>1</sup> | GA | November 10, 2026 |
+| [.NET 8 (LTS)](https://dotnet.microsoft.com/platform/support/policy/dotnet-core#lifecycle) | GA | November 10, 2026 |
 | [.NET 6 (LTS)](https://dotnet.microsoft.com/platform/support/policy/dotnet-core#lifecycle) | GA | November 12, 2024 |
 
-<sup>1</sup> Targeting .NET 8 with the in-process model is not yet enabled for apps in sovereign clouds. Updates will be communicated on [this tracking thread on GitHub](https://github.com/Azure/azure-functions-host/issues/9951).
-
 For more information, see [Develop C# class library functions using Azure Functions](../articles/azure-functions/functions-dotnet-class-library.md). Also supports [C# script functions](../articles/azure-functions/functions-reference-csharp.md).
 
 ### [v1.x](#tab/v1/in-process)