Skip to content

Commit f980671

Browse files
committed
changes
1 parent 719494d commit f980671

File tree

3 files changed

+5
-5
lines changed

3 files changed

+5
-5
lines changed

articles/postgresql/flexible-server/concepts-compare-single-server-flexible-server.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -114,8 +114,8 @@ The following table provides a list of high-level features and capabilities comp
114114
| PgCron, lo, pglogical | No | Yes |
115115
| pgAudit | Preview | Yes |
116116
| **Security** | | |
117-
| Azure Active Directory Support(AAD) | Yes | Preview |
118-
| Customer managed encryption key(BYOK) | Yes | Preview |
117+
| Azure Active Directory Support(AAD) | Yes | Yes |
118+
| Customer managed encryption key(BYOK) | Yes | Yes |
119119
| SCRAM Authentication (SHA-256) | No | Yes |
120120
| Secure Sockets Layer support (SSL) | Yes | Yes |
121121
| **Other features** | | |

articles/postgresql/flexible-server/concepts-data-encryption.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ When you're using data encryption by using a customer-managed key, here are reco
103103
:::image type="content" source="media/concepts-data-encryption/key-vault-trusted-service.png" alt-text="Screenshot of an image of networking screen with trusted-service-with-AKV setting." lightbox="media/concepts-data-encryption/key-vault-trusted-service.png":::
104104

105105
> [!NOTE]
106-
>Important to note, that after choosing **disable public access** option in Azure Key Vault networking and allowing only *trusted Microsoft* services you may see error similar to following : *You have enabled the network access control. Only allowed networks will have access to this key vault* while attempting to administer Azure Key Vault via portal through public access, since portal is not considered to be trusted service.
106+
>Important to note, that after choosing **disable public access** option in Azure Key Vault networking and allowing only *trusted Microsoft* services you may see error similar to following : *You have enabled the network access control. Only allowed networks will have access to this key vault* while attempting to administer Azure Key Vault via portal through public access.
107107
108108
Here are recommendations for configuring a customer-managed key:
109109

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,8 +17,8 @@ ms.custom:
1717

1818
[!INCLUDE [applies-to-postgresql-Flexible-server](../includes/applies-to-postgresql-Flexible-server.md)]
1919

20-
> [!NOTE]
21-
> Azure Active Directory Authentication for PostgreSQL Flexible Server is currently in preview.
20+
21+
2222

2323
You can use both system-assigned and user-assigned managed identities to authenticate to Azure Database for PostgreSQL. This article shows you how to use a system-assigned managed identity for an Azure Virtual Machine (VM) to access an Azure Database for PostgreSQL server. Managed Identities are automatically managed by Azure and enable you to authenticate to services that support Azure AD authentication without needing to insert credentials into your code.
2424

0 commit comments

Comments
 (0)