Skip to content

Commit 5c7aa48

Browse files
committed
Preview removal
1 parent c3d0e66 commit 5c7aa48

File tree

2 files changed

+5
-21
lines changed

2 files changed

+5
-21
lines changed

articles/cosmos-db/postgresql/concepts-authentication.md

Lines changed: 2 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -6,21 +6,13 @@ ms.author: nlarin
66
ms.service: cosmos-db
77
ms.subservice: postgresql
88
ms.topic: conceptual
9-
ms.date: 01/17/2024
9+
ms.date: 02/06/2024
1010
---
1111

1212
# Microsoft Entra ID and PostgreSQL authentication with Azure Cosmos DB for PostgreSQL
1313

1414
[!INCLUDE [PostgreSQL](../includes/appliesto-postgresql.md)]
1515

16-
> [!IMPORTANT]
17-
> Microsoft Entra ID (formerly Azure Active Directory) authentication in Azure Cosmos DB for PostgreSQL is currently in preview.
18-
> This preview version is provided without a service level agreement, and it's not recommended
19-
> for production workloads. Certain features might not be supported or might have constrained
20-
> capabilities.
21-
>
22-
> You can see a complete list of other new features in [preview features](product-updates.md#features-in-preview).
23-
2416
Azure Cosmos DB for PostgreSQL supports PostgreSQL authentication and integration with Microsoft Entra ID. Each Azure Cosmos DB for PostgreSQL cluster is created with native PostgreSQL authentication enabled and one built-in PostgreSQL role named `citus`. You can add more native PostgreSQL roles after cluster provisioning is completed.
2517

2618
You can also enable Microsoft Entra ID (formerly Azure Active Directory) authentication on a cluster in addition to the PostgreSQL authentication method or instead of it. You can configure authentication methods on each Azure Cosmos DB for PostgreSQL cluster independently. If you need to change authentication method, you can do it at any time after cluster provisioning is completed. Changing authentication methods doesn't require cluster restart.
@@ -63,7 +55,7 @@ Notably, the `citus` role has some restrictions:
6355

6456
<a name='azure-active-directory-authentication-preview'></a>
6557

66-
## Microsoft Entra ID authentication (preview)
58+
## Microsoft Entra ID authentication
6759

6860
[Microsoft Entra ID](/entra/fundamentals/whatis) (formerly Azure Active Directory) authentication is a mechanism of connecting to Azure Cosmos DB for PostgreSQL using identities defined in Microsoft Entra ID. With Microsoft Entra ID authentication, you can manage database user identities and other Microsoft services in a central location, which simplifies permission management.
6961

articles/cosmos-db/postgresql/how-to-configure-authentication.md

Lines changed: 3 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -6,21 +6,13 @@ ms.author: nlarin
66
ms.service: cosmos-db
77
ms.subservice: postgresql
88
ms.topic: how-to
9-
ms.date: 01/18/2024
9+
ms.date: 02/06/2024
1010
---
1111

1212
# Use Microsoft Entra ID and native PostgreSQL roles for authentication with Azure Cosmos DB for PostgreSQL
1313

1414
[!INCLUDE [PostgreSQL](../includes/appliesto-postgresql.md)]
1515

16-
> [!IMPORTANT]
17-
> Microsoft Entra ID (formerly Azure Active Directory) authentication in Azure Cosmos DB for PostgreSQL is currently in preview.
18-
> This preview version is provided without a service level agreement, and it's not recommended
19-
> for production workloads. Certain features might not be supported or might have constrained
20-
> capabilities.
21-
>
22-
> You can see a complete list of other new features in [preview features](product-updates.md#features-in-preview).
23-
2416
In this article, you configure authentication methods for Azure Cosmos DB for PostgreSQL. You manage Microsoft Entra ID admin users and native PostgreSQL roles for authentication with Azure Cosmos DB for PostgreSQL. You also learn how to use a Microsoft Entra ID token with Azure Cosmos DB for PostgreSQL.
2517

2618
An Azure Cosmos DB for PostgreSQL cluster is created with one built-in native PostgreSQL role named 'citus'. You can add more native PostgreSQL roles after cluster provisioning is completed.
@@ -33,7 +25,7 @@ You need to use Azure portal to configure authentication methods on an Azure Cos
3325
Complete the following items on your Azure Cosmos DB for PostgreSQL cluster to enable or disable Microsoft Entra ID authentication and native PostgreSQL authentication.
3426

3527
1. On the cluster page, under the **Cluster management** heading, choose **Authentication** to open authentication management options.
36-
1. In **Authentication methods** section, choose **PostgreSQL authentication only**, **Microsoft Entra ID authentication (preview)**, or **PostgreSQL and Microsoft Entra ID authentication (preview)** as the authentication method based on your requirements.
28+
1. In **Authentication methods** section, choose **PostgreSQL authentication only**, **Microsoft Entra ID authentication**, or **PostgreSQL and Microsoft Entra ID authentication** as the authentication method based on your requirements.
3729

3830
Once done proceed with [configuring Microsoft Entra ID authentication](#configure-azure-active-directory-authentication) or [adding native PostgreSQL roles](#configure-native-postgresql-authentication) on the same **Authentication** page.
3931

@@ -71,7 +63,7 @@ az ad sp update --id b4fa09d8-5da5-4352-83d9-05c2a44cf431 --set accountEnabled=t
7163

7264
To add or remove Microsoft Entra ID roles on cluster, follow these steps on **Authentication** page:
7365

74-
1. In **Microsoft Entra ID authentication (preview)** section, select **Add Microsoft Entra ID admins**.
66+
1. In **Microsoft Entra ID authentication** section, select **Add Microsoft Entra ID admins**.
7567
1. In **Select Microsoft Entra ID Admins** panel, select one or more valid Microsoft Entra ID user or enterprise application in the current AD tenant to be a Microsoft Entra ID administrator on your Azure Cosmos DB for PostgreSQL cluster.
7668
1. Use **Select** to confirm your choice.
7769
1. In the **Authentication** page, select **Save** in the toolbar to save changes or proceed with adding native PostgreSQL roles.

0 commit comments

Comments
 (0)