Skip to content

Commit ea8a4c0

Browse files
Merge pull request #231023 from kabharati/patch-51
Update concepts-azure-ad-authentication.md
2 parents 46c4235 + 9548e18 commit ea8a4c0

File tree

1 file changed

+0
-5
lines changed

1 file changed

+0
-5
lines changed

articles/postgresql/flexible-server/concepts-azure-ad-authentication.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -89,11 +89,6 @@ Once you've authenticated against the Active Directory, you then retrieve a toke
8989
9090
- Azure Database for PostgreSQL Flexible Server matches access tokens to the database role using the user’s unique Azure Active Directory user ID, as opposed to using the username. If an Azure AD user is deleted and a new user is created with the same name, Azure Database for PostgreSQL Flexible Server considers that a different user. Therefore, if a user is deleted from Azure AD and a new user is added with the same name the new user won't be able to connect with the existing role.
9191

92-
## Limitations
93-
94-
- PG bouncer is currently supported for newly created servers and we are going to support existing servers very soon..
95-
96-
9792

9893
## Next steps
9994

0 commit comments

Comments
 (0)