microsoft / microsoft/fhir-server
Azure SQL - Entra authentication
Nobody has claimed this yet.
- Dominant language
- TSQL
- Stars
- 1.4k
- Forks
- 592
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 41
Description
Hi,
We currently run the OSS version via an Azure App Service connecting to an Azure SQL database. This was setup initially a few years back from the deployment script. This connects to the database via the fhirAdmin user. We would like to change this to connect to the database via Entra ID, specifically the managed identify of the app service. Is it documented anywhere (I can't find it) what the minimal permissions for the managed identity sql user is? Note - we do not do schema updates via the app service (we use the dotnet tool for this).
Thanks,
Reuben
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the deployment script referenced in the issue and trace how the Azure App Service connects to Azure SQL as fhirAdmin. Compare that setup with the separate dotnet tool used for schema updates, then document the minimal permissions required for the App Service managed identity and verify that schema permissions are excluded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, sql
- Domain
- authentication, cloud, database
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100