Not able to use Managed Identity for Function App to access Azure Files (SMB)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure
- Domain
- cloud, infrastructure
Research direction
The issue names no repository files, tests, or entry point. Start by reviewing the Marketplace deployment configuration and how it selects the Function App Service Plan and Azure Files settings. Done should be a supported deployment path that avoids the access-key-backed SMB dependency while preserving Function App deployment.
Written by the indexing model from the issue text.
Description
Describe the bug
this version relies on an Azure Function deployed on a Consumption App Service Plan, which automatically creates two settings:
WEBSITE_CONTENTAZUREFILECONNECTIONSTRING
WEBSITE_CONTENTSHARE
These settings use Access Keys to connect to the Azure Files (SMB) share. Unfortunately, Azure Files does not support Managed Identity connections, and these settings cannot be removed once created.
To Reproduce
Steps to reproduce the behavior:
Disabling Storage Account Keys.
Expected behavior
Because a security initiative, we need to get rid of Storage Account Keys and use Managed Identity instead.
Additional context
Deploy the Function App on a Dedicated App Service Plan, which allows you to avoid these settings and eliminates the dependency on Azure Files.
Since the deployment comes directly from the Azure Marketplace, it’s likely managed and may not allow customization of the App Service Plan or its settings.
- Dominant language
- No language data
- Stars
- 58
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from microsoft/startstopv2-deployments
-
.NET version supportOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/startstopv2-deployments#155 · 3 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
microsoft/startstopv2-deployments#149 · 2 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 10/100
All issues in microsoft/startstopv2-deployments
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pydantic/pydantic-ai#8935 ·
Maintainers usually reply within 1 day
-
Language: Terraform :globe_with_meridians: Needs: Triage :mag: Type: Bug :bug:
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Azure/terraform-azurerm-avm-res-web-site#408 · 1 comment ·
Maintainers usually reply within 1 day
-
Needs: Triage :mag: Product: Terraform (AVM) Topic: Networking (HS) :globe_with_meridians:
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Azure/Azure-Landing-Zones#4291 · 1 comment ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
cloudtools/troposphere#2367 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
googleapis/google-cloud-dart#366 ·
Maintainers usually reply within 1 day