Pull Reference Values in App Service Environment Variables Not Working

Open

#1,155 opened on Jun 23, 2026 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 48/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Quiet
Tech stack: azure
Domain: cloud

Research direction

Start by reproducing the issue with an App Service environment variable referencing Azure App Configuration, then update the referenced value and use the Environment Variables tab's “Pull Reference Values” action. Check the activity log and the application's environment variables after the action and a manual restart. Done means the action refreshes the referenced value and the App Service reflects it.

Written by the indexing model from the issue text.

Description

Summary

When using App Configuration references with App Service environment variables, the "Pull Reference Values" button is not refreshing the environment variables provided to the App Service. When you click the button, it does state:

This will query Key Vault and App Configuration to update any values referenced by the app. Your site will restart in order to apply the new configuration.

However, nothing indicates that the app was restarted and the environment variable values within the App Service remain the same. I also tried manually restarting the app service after pulling the reference values, but there was no change.

Steps to recreate:

Use references to App Configuration in an App Service's environment variables. Example: @Microsoft.AppConfiguration(Endpoint=https://redacted.azconfig.io; Key=app:debug; Label=poc)
Update a referenced value in App Configuration
Navigate to the App Service's Environment Variables tab and choose "Pull Reference Values"
Check activity log to see if app service has been restarted
Observe environment variable values within the application and confirm no change

Dominant language: No language data
Stars: 263
Forks: 82
Avg merge: 3d 15h
Merged PRs (30d): 6

Contributor guide

No contributing guide indexed for this repository

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.

Similar issues

[AVM Module Issue]: Module Validation rules does not allow cache rules unless Premium SKU, yet cache rules are supported with non-Premium SKUs Open

Language: Terraform :globe_with_meridians: Needs: Triage :mag: Type: Bug :bug:

Difficulty 2/5 1-3 hours Newbie friendliness 68/100

Azure/terraform-azurerm-avm-res-containerregistry-registry#230 · 1 comment · Opened Sep 22, 2026
[BUG] GkeTpuCluster queries metadata.google.internal for MEGASCALE_SLICE_ID even when TPU_SKIP_MDS_QUERY is set Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

jax-ml/jax#40854 · Opened Sep 22, 2026
fix(mcp): `permanently_delete_cloud_{source,destination,connection}` lack `workspace_id` param, unusable without a default workspace Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

airbytehq/PyAirbyte#1201 · Opened Sep 21, 2026
[BUG] Route53Resolver: CreateResolverEndpoint requires IpAddressRequests, but the AWS member is IpAddresses, so no SDK client can call it Open

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

floci-io/floci#4108 · Opened Sep 21, 2026
wm_gcp_parse_output underflows its heap buffer by one byte Open

level/task module/gcp type/bug

Difficulty 2/5 1-3 hours Newbie friendliness 85/100

wazuh/wazuh#39525 · Opened Sep 21, 2026

More Cloud issues