Merge pull request #270379 from markingmyname/charles

update articles

Author: prmerger-automator[bot]

articles/postgresql/flexible-server/how-to-connect-with-managed-identity.md

@@ -25,8 +25,8 @@ You learn how to:
 
 ## Prerequisites
 
-- If you're not familiar with the managed identities for Azure resources feature, see this [overview](../../../articles/active-directory/managed-identities-azure-resources/overview.md). If you don't have an Azure account, [sign up for a free account](https://azure.microsoft.com/free/) before you continue.
-- To do the required resource creation and role management, your account needs "Owner" permissions at the appropriate scope (your subscription or resource group). If you need assistance with a role assignment, see [Assign Azure roles to manage access to your Azure subscription resources](../../../articles/role-based-access-control/role-assignments-portal.md).
+- If you're not familiar with the managed identities for Azure resources feature, visit [What are managed identities for Azure resources?](/entra/identity/managed-identities-azure-resources/overview). If you don't have an Azure account, [sign up for a free account](https://azure.microsoft.com/free/) before you continue.
+- To do the required resource creation and role management, your account needs "Owner" permissions at the appropriate scope (your subscription or resource group). If you need assistance with a role assignment, see [Assign Azure roles using the Azure portal](../../../articles/role-based-access-control/role-assignments-portal.md).
 - You need an Azure VM (for example, running Ubuntu Linux) that you'd like to use to access your database using Managed Identity
 - You need an Azure Database for PostgreSQL flexible server instance that has [Microsoft Entra authentication](how-to-configure-sign-in-azure-ad-authentication.md) configured
 - To follow the C# example, first, complete the guide on how to [Connect with C#](connect-csharp.md)

articles/postgresql/hyperscale/moved.md

@@ -12,21 +12,17 @@ ms.date: 09/24/2023
 
 # Azure Database for PostgreSQL - Hyperscale (Citus) is now Azure Cosmos DB for PostgreSQL
 
-Existing Hyperscale (Citus) server groups automatically became [Azure
-Cosmos DB for PostgreSQL](../../cosmos-db/postgresql/introduction.md) clusters
-under the new name in October 2022.  All features and pricing, including
-reserved compute pricing and regional availability, were preserved under the
-new name.
+Existing Hyperscale (Citus) server groups automatically became [Azure Cosmos DB for PostgreSQL](../../cosmos-db/postgresql/introduction.md) clusters under the new name in October 2022. All features and pricing, including reserved compute pricing and regional availability, were preserved under the new name.
 
 ## Find your cluster in the renamed service
 
 View the list of Azure Cosmos DB for PostgreSQL clusters in your subscription.
 
-# [Direct link](#tab/direct)
+#### [Direct link](#tab/direct)
 
 Go to the [list of Azure Cosmos DB for PostgreSQL clusters](https://portal.azure.com/#browse/Microsoft.DBforPostgreSQL%2FserverGroupsv2) in the Azure portal.
 
-# [Portal search](#tab/portal-search)
+#### [Portal search](#tab/portal-search)
 
 In the [Azure portal](https://portal.azure.com), search for `postgresql` and
 select **Azure Cosmos DB for PostgreSQL Cluster** from the results.

articles/postgresql/single-server/concepts-data-access-and-security-private-link.md

@@ -50,7 +50,7 @@ With Private Link, you can enable cross-premises access to the private endpoint
 
 > [!NOTE]
 > In some cases the Azure Database for PostgreSQL and the VNet-subnet are in different subscriptions. In these cases you must ensure the following configurations:
-> - Make sure that both the subscription has the **Microsoft.DBforPostgreSQL** resource provider registered. For more information, refer to [resource-manager-registration][resource-manager-portal]
+> - Make sure that both the subscription has the **Microsoft.DBforPostgreSQL** resource provider registered. 
 
 ## Configure Private Link for Azure Database for PostgreSQL Single server
 
@@ -122,22 +122,22 @@ If you want to rely only on private endpoints for accessing their Azure Database
 
 When this setting is set to *YES* only connections via private endpoints are allowed to your Azure Database for PostgreSQL. When this setting is set to *NO* clients can connect to your Azure Database for PostgreSQL based on your firewall or VNet service endpoint setting. Additionally, once the value of the Private network access is set, customers cannot add and/or update existing 'Firewall rules' and 'VNet service endpoint rules'.
 
-> [!Note]
+> [!NOTE]
 > This feature is available in all Azure regions where Azure Database for PostgreSQL - Single server supports General Purpose and Memory Optimized pricing tiers.
 >
 > This setting does not have any impact on the SSL and TLS configurations for your Azure Database for PostgreSQL Single server.
 
 To learn how to set the **Deny Public Network Access** for your Azure Database for PostgreSQL Single server from Azure portal, refer to [How to configure Deny Public Network Access](how-to-deny-public-network-access.md).
 
-## Next steps
+## Related content
 
 To learn more about Azure Database for PostgreSQL Single server security features, see the following articles:
 
-* To configure a firewall for Azure Database for PostgreSQL Single server, see [Firewall support](./concepts-firewall-rules.md).
+- To configure a firewall for Azure Database for PostgreSQL Single server, see [Firewall support](./concepts-firewall-rules.md).
 
-* To learn how to configure a virtual network service endpoint for your Azure Database for PostgreSQL Single server, see [Configure access from virtual networks](./concepts-data-access-and-security-vnet.md).
+- To learn how to configure a virtual network service endpoint for your Azure Database for PostgreSQL Single server, see [Configure access from virtual networks](./concepts-data-access-and-security-vnet.md).
 
-* For an overview of Azure Database for PostgreSQL Single server connectivity, see [Azure Database for PostgreSQL Connectivity Architecture](./concepts-connectivity-architecture.md)
+- For an overview of Azure Database for PostgreSQL Single server connectivity, see [Azure Database for PostgreSQL Connectivity Architecture](./concepts-connectivity-architecture.md)
 
 <!-- Link references, to text, Within this same GitHub repo. -->
 [resource-manager-portal]: ../../azure-resource-manager/management/resource-providers-and-types.md