anthonydresser / testissues

0 stars 0 forks source link

Azure AD authenticated user permission change not reflected unless account removed and re-added #5025

Open anthonydresser opened 3 years ago

anthonydresser commented 3 years ago

Steps to Reproduce:

  1. Azure SQL, create users based on AD groups (e.g. Create user [db-readers] FROM EXTERNAL PROVIDER; grant roles as appropriate)
  2. Add team member to that group in Azure AD.
  3. They connect to DB with ADS using Azure AD authentication and are able to log in and do their stuff 👍
  4. Add the team member to an elevated privilege group (e.g. db writers) in Azure AD
  5. Disconnect and reconnect to the Server/DB and try and modify data - fails 👎
  6. AD account has to be removed in ADS and re-added to pick up new permissions.

We are currently manually doing the group membership changes in AD but will be looking at using PIM in future so would hope this scenario would work out of the box.

Are we doing something wrong?