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

Author: HeidiSteen

articles/active-directory/hybrid/connect/how-to-connect-group-writeback-v2.md

@@ -135,6 +135,7 @@ These limitations and known issues are specific to group writeback:
 - Group Writeback does not support writeback of nested group members that have a scope of ‘Domain local’ in AD, since Azure AD security groups are written back with scope ‘Universal’. If you have a nested group like this, you'll see an export error in Azure AD Connect with the message “A universal group cannot have a local group as a member.”  The resolution is to remove the member with scope ‘Domain local’ from the Azure AD group or update the nested group member scope in AD to ‘Global’ or ‘Universal’ group. 
 - Nested cloud groups that are members of writeback enabled groups must also be enabled for writeback to remain nested in AD. 
 - Group Writeback setting to manage new security group writeback at scale is not yet available. You will need to configure writeback for each group.  
+- Group Writeback only supports writing back groups to a single Organization Unit (OU).
 
 ## Next steps 
 

articles/ddos-protection/ddos-protection-sku-comparison.md

@@ -5,7 +5,7 @@ author: AbdullahBell
 ms.author: Abell
 ms.service: ddos-protection
 ms.topic: conceptual 
-ms.date: 05/01/2023
+ms.date: 05/11/2023
 ms.custom: template-concept, ignite-2022
 ---
 
@@ -59,7 +59,7 @@ DDoS Network Protection and DDoS IP Protection have the following limitations:
 - PaaS services (multi-tenant), which includes Azure App Service Environment for Power Apps, Azure API Management in deployment modes other than those supported above, or Azure Virtual WAN aren't currently supported. 
 - Protecting a public IP resource attached to a NAT Gateway isn't supported.
 - Virtual machines in Classic/RDFE deployments aren't supported.
-- Scenarios in which a single VM is running behind a public IP isn't supported. 
+- Scenarios in which a single VM is running behind a public IP is not recommended. For more information, see [Fundamental best practices](./fundamental-best-practices.md#design-for-scalability)
 - Protected resources that include public IP address prefix, or public IP created from public IP address prefix aren't supported. Azure Load Balancer with a public IP created from a public IP prefix is supported.
 
 DDoS IP Protection is similar to Network Protection, but has the following additional limitation:

articles/digital-twins/concepts-apis-sdks.md

@@ -73,7 +73,7 @@ The available helper classes are:
 
 ## Bulk import with the Jobs API
 
-The [Jobs API](/rest/api/digital-twins/dataplane/import-jobs) is a data plane API that allows you to import a set of models, twins, and/or relationships in a single API call. Jobs API operations are also included with the [CLI commands](/cli/azure/dt/job) and [data plane SDKs](#data-plane-apis). Using the Jobs API requires use of [Azure Blob Storage](../storage/blobs/storage-blobs-introduction.md). 
+The [Jobs API](/rest/api/digital-twins/dataplane/import-jobs) (currently in preview) is a data plane API that allows you to import a set of models, twins, and/or relationships in a single API call. Jobs API operations are also included with the [CLI commands](/cli/azure/dt/job) and [data plane SDKs](#data-plane-apis). Using the Jobs API requires use of [Azure Blob Storage](../storage/blobs/storage-blobs-introduction.md). 
 
 ### Check permissions
 

articles/digital-twins/how-to-manage-graph.md

@@ -78,7 +78,7 @@ You can even create multiple instances of the same type of relationship between
 
 ### Create relationships in bulk with the Jobs API
 
-You can use the [Jobs API](concepts-apis-sdks.md#bulk-import-with-the-jobs-api) to create many relationships at once in a single API call. This method requires the use of [Azure Blob Storage](../storage/blobs/storage-blobs-introduction.md), as well as [write permissions](concepts-apis-sdks.md#check-permissions) in your Azure Digital Twins instance for relationships and bulk jobs.
+You can use the [Jobs API](concepts-apis-sdks.md#bulk-import-with-the-jobs-api) (currently in preview) to create many relationships at once in a single API call. This method requires the use of [Azure Blob Storage](../storage/blobs/storage-blobs-introduction.md), as well as [write permissions](concepts-apis-sdks.md#check-permissions) in your Azure Digital Twins instance for relationships and bulk jobs.
 
 >[!TIP]
 >The Jobs API also allows models and twins to be imported in the same call, to create all parts of a graph at once. For more about this process, see [Upload models, twins, and relationships in bulk with the Jobs API](#upload-models-twins-and-relationships-in-bulk-with-the-jobs-api).
@@ -180,7 +180,7 @@ This section describes strategies for creating a graph with multiple elements at
 
 ### Upload models, twins, and relationships in bulk with the Jobs API
 
-You can use the [Jobs API](concepts-apis-sdks.md#bulk-import-with-the-jobs-api) to upload multiple models, twins, and relationships to your instance in a single API call, effectively creating the graph all at once. This method requires the use of [Azure Blob Storage](../storage/blobs/storage-blobs-introduction.md), as well as [write permissions](concepts-apis-sdks.md#check-permissions) in your Azure Digital Twins instance for graph elements (models, twins, and relationships) and bulk jobs.
+You can use the [Jobs API](concepts-apis-sdks.md#bulk-import-with-the-jobs-api) (currently in preview) to upload multiple models, twins, and relationships to your instance in a single API call, effectively creating the graph all at once. This method requires the use of [Azure Blob Storage](../storage/blobs/storage-blobs-introduction.md), as well as [write permissions](concepts-apis-sdks.md#check-permissions) in your Azure Digital Twins instance for graph elements (models, twins, and relationships) and bulk jobs.
 
 To import resources in bulk, start by creating an *NDJSON* file containing the details of your resources. The file starts with a `Header` section, followed by the optional sections `Models`, `Twins`, and `Relationships`. You don't have to include all three types of graph data in the file, but any sections that are present must follow that order. Twins defined in the file can reference models that are either defined in this file or already present in the instance, and they can optionally include initialization of the twin's properties. Relationships defined in the file can reference twins that are either defined in this file or already present in the instance, and they can optionally include initialization of relationship properties.
 

articles/digital-twins/how-to-manage-model.md

@@ -91,7 +91,7 @@ If you're using the [REST APIs](/rest/api/azure-digitaltwins/) or [Azure CLI](/c
 
 ### Upload large model sets with the Jobs API
 
-For large model sets, you can use the [Jobs API](concepts-apis-sdks.md#bulk-import-with-the-jobs-api) to upload many models at once in a single API call. The API can simultaneously accept up to the [Azure Digital Twins limit for number of models in an instance](reference-service-limits.md), and it automatically reorders models if needed to resolve dependencies between them. This method requires the use of [Azure Blob Storage](../storage/blobs/storage-blobs-introduction.md), as well as [write permissions](concepts-apis-sdks.md#check-permissions) in your Azure Digital Twins instance for models and bulk jobs.
+For large model sets, you can use the [Jobs API](concepts-apis-sdks.md#bulk-import-with-the-jobs-api) (currently in preview) to upload many models at once in a single API call. The API can simultaneously accept up to the [Azure Digital Twins limit for number of models in an instance](reference-service-limits.md), and it automatically reorders models if needed to resolve dependencies between them. This method requires the use of [Azure Blob Storage](../storage/blobs/storage-blobs-introduction.md), as well as [write permissions](concepts-apis-sdks.md#check-permissions) in your Azure Digital Twins instance for models and bulk jobs.
 
 >[!TIP]
 >The Jobs API also allows twins and relationships to be imported in the same call, to create all parts of a graph at once. For more about this process, see [Upload models, twins, and relationships in bulk with the Jobs API](how-to-manage-graph.md#upload-models-twins-and-relationships-in-bulk-with-the-jobs-api).

articles/digital-twins/how-to-manage-twin.md

@@ -82,7 +82,7 @@ The helper class of `BasicDigitalTwin` allows you to store property fields in a
 
 ### Create twins in bulk with the Jobs API
 
-You can use the [Jobs API](concepts-apis-sdks.md#bulk-import-with-the-jobs-api) to create many twins at once in a single API call. This method requires the use of [Azure Blob Storage](../storage/blobs/storage-blobs-introduction.md), as well as [write permissions](concepts-apis-sdks.md#check-permissions) in your Azure Digital Twins instance for twins and bulk jobs.
+You can use the [Jobs API](concepts-apis-sdks.md#bulk-import-with-the-jobs-api) (currently in preview) to create many twins at once in a single API call. This method requires the use of [Azure Blob Storage](../storage/blobs/storage-blobs-introduction.md), as well as [write permissions](concepts-apis-sdks.md#check-permissions) in your Azure Digital Twins instance for twins and bulk jobs.
 
 >[!TIP]
 >The Jobs API also allows models and relationships to be imported in the same call, to create all parts of a graph at once. For more about this process, see [Upload models, twins, and relationships in bulk with the Jobs API](how-to-manage-graph.md#upload-models-twins-and-relationships-in-bulk-with-the-jobs-api).

articles/postgresql/flexible-server/concepts-supported-versions.md

@@ -15,6 +15,11 @@ ms.date: 08/25/2022
 
 Azure Database for PostgreSQL - Flexible Server currently supports the following major versions:
 
+## PostgreSQL version 15 (Preview)
+
+PostgreSQL version 15 is now available in public preview in limited regions (West Europe, East US, West US2, South East Asia, UK SOuth, North Europe, Japan east). Refer to the [PostgreSQL documentation](https://www.postgresql.org/about/news/postgresql-15-released-2526/) to learn more about improvements and fixes in this release. New servers will be created with this minor version.
+
+
 ## PostgreSQL version 14
 
 The current minor release is **14.7**. Refer to the [PostgreSQL documentation](https://www.postgresql.org/docs/release/14.7/) to learn more about improvements and fixes in this release. New servers will be created with this minor version.

articles/private-5g-core/azure-stack-edge-packet-core-compatibility.md

@@ -1,6 +1,6 @@
 ---
 title: Packet core and Azure Stack Edge compatibility
-description: Discover which Azure Stack Edge versions are compatible with each packet core version
+description: Discover which Azure Stack Edge models and versions are compatible with each packet core version
 author: liumichelle
 ms.author: limichel
 ms.service: private-5g-core
@@ -10,9 +10,19 @@ ms.date: 03/30/2023
 
 # Packet core and Azure Stack Edge (ASE) compatibility
 
-Each site in your deployment contains an Azure Stack Edge (ASE) Pro device that hosts a packet core instance. This article provides information on version compatibility between ASE and packet core that you can refer to when installing a packet core instance or performing an upgrade.
+Each site in your deployment contains an Azure Stack Edge (ASE) Pro device that hosts a single packet core instance. This article provides information on version compatibility between ASE and packet core that you can refer to when installing a packet core instance or performing an upgrade.
 
-## Packet core and ASE compatibility table
+## Supported Azure Stack Edge Pro models
+
+The following Azure Stack Edge Pro models are supported:
+
+- Azure Stack Edge Pro with GPU
+- Azure Stack Edge Pro 2
+  - Model 64G2T
+  - Model 128G4T1GPU
+  - Model 256G6T2GPU
+
+## Packet core and Azure Stack Edge version compatibility table
 
 The following table provides information on which versions of the ASE device are compatible with each packet core version.
 

articles/private-5g-core/azure-stack-edge-virtual-machine-sizing.md

@@ -1,8 +1,8 @@
 ---
 title: Azure Stack Edge virtual machine sizing
 description: Learn about the VMs that Azure Private 5G Core uses when running on an Azure Stack Edge device.
-author: b-branco
-ms.author: biancabranco
+author: robswain
+ms.author: robswain
 ms.service: private-5g-core
 ms.topic: reference
 ms.date: 01/27/2023
@@ -18,12 +18,12 @@ The following table contains information about the VMs that Azure Private 5G Cor
 | AP5GC Cluster Control Plane VM | Standard_F4s_v1 | 4 | 4 | Ephemeral - 128 GB | Control Plane of the Kubernetes cluster used for AP5GC |
 | AP5GC Cluster Node VM | Standard_F16s_HPN | 16 | 32 | Ephemeral - 128 GB </br> Persistent - 102 GB | AP5GC workload node |
 
-## Remaining usable resource on ASE Pro GPU
+## Remaining usable resource on Azure Stack Edge Pro
 
 The following resources are available within ASE after deploying AP5GC. You can use these resources, for example, to deploy additional virtual machines or storage accounts.
 
-| Resource | Value |
-|--|--|
-| vCPUs | 16 |
-| Memory | 56 GB |
-| Storage | ~3.75 TB |
+| Resource | Pro with GPU | Pro 2 - 64G2T | Pro 2 - 128G4T1GPU | Pro 2 - 256G6T2GPU |
+|----------|--------------|---------------|--------------------|--------------------|
+| vCPUs    | 16           | 4             | 4                  | 4                  |
+| Memory   | 56 GB        | 3 GB          | 51 GB              | 163 GB             |
+| Storage  | ~3.75 TB     | ~280 GB       | ~1.1 TB            | ~2.0 TB            |