Small and medium business | Business Central, N...

Azure Blob Storage Integration Works in PRODUCTION but Fails in DEVELOPMENT Environment

(5) Share

Report

Posted on by Nimsara Jayathilaka.

4,950 Super User 2026 Season 1

Hello Community,

I am facing an issue with Azure Blob Storage integration in Business Central.

In PRODUCTION, the connection and operations (upload/view blobs) work perfectly.
In the DEVELOPMENT environment, the same code was working until a few days ago, but now it fails.
Currently, I cannot upload or view any blob-related activities in the DEV environment, and I get an error (unfortunately, no changes were made to the code

Has anyone experienced this issue before? Could it be related to:

Azure Storage Account permissions/keys?
Environment-specific setup differences?
A recent update in Business Central or Azure affecting DEV only

Any guidance or troubleshooting steps would be highly appreciated.

Thanks in advance!

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (8)

Answers (0)

Suggested answer

Sahan Hasitha 2,683 on at

Like (2)

Report
Copy link

Link copied!

hi

checking the storage keys/permissions and environment-specific settings, as these are the most common causes when the same code suddenly fails in one environment.

try this

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/integration-azure-overview

Was this reply helpful? Yes No
Suggested answer

Sumit Singh 11,757 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!
Hi Nimsara,

Checklist (DEV vs PROD Azure Blob issues in Business Central):
1) Re‑auth / Secrets

If you use account keys / SAS, confirm the key wasn’t rotated and regenerate SAS; key rotation invalidates account‑level SAS. Update the DEV secret/connection string. Manage access keys · Key rotation impact on SAS

Prefer Microsoft Entra ID (RBAC) over shared keys; ensure the app/service principal has a Storage Blob Data * role on the container/account. Authorize with Entra ID · Portal auth methods & required permissions

2) Network restrictions

Compare Firewalls & VNets between PROD and DEV storage accounts; allow the DEV caller’s IP/VNet or trusted services as needed. Storage firewall rules

3) Public/anonymous access setting (if applicable)

If DEV relied on anonymous reads, check “Allow blob public access” at account level and container access level; defaults are private. Anonymous access configuration

4) Business Central side

Verify you’re using the System Application’s Azure Blob module (e.g., ABS Blob Client) and its auth implementation is consistent across environments; confirm any recent BC/SaaS update didn’t change module/API version or permissions. Azure integrations overview (BC) · ABS Blob Client codeunit docs

5) SAS/token validity

Intermittent “Server failed to authenticate…” often points to expired/insufficient SAS. Recreate with the right scope/permissions. MS Q&A—SAS/token auth failures

Quick next steps:

Re‑generate a fresh SAS (or switch to Entra ID + RBAC) and update DEV secrets; re‑test. [Keys/SAS best practices]

Compare network rules and anonymous access settings between PROD/DEV storage accounts. Firewall rules · Anonymous access

If still failing, log the HTTP status + error body from your HttpClient call in BC to pinpoint auth vs network vs container issues (use the ABS module methods). ABS Blob Client

Mark true, “Does this answer your question” if it helps.

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Rishabh Kanaskar 6,219 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Yes, this is usually environment-specific. Check the following in your DEV environment:
> Azure Storage Account Keys / SAS Token – verify they haven’t expired or changed.
> Connection String / Endpoint – ensure it matches the DEV storage account and is correct in the BC service connection.
> Permissions – confirm the DEV identity (service principal or user) has proper Blob Contributor / Reader roles.
> BC Environment Settings – check Azure AD App registration or BC Web Service Access Key if used.
> Recent Updates – compare BC version in DEV vs PROD; sometimes minor updates affect TLS/SSL or authentication.

Troubleshooting steps:
> Try a simple blob access test outside BC (e.g., Azure Storage Explorer) with the DEV credentials.
> Review AL error logs for detailed exception messages.
> Revalidate all secrets and refresh tokens if using OAuth.

Thanks

Rishabh

Was this reply helpful? Yes No
CU27090804-0 on at

Like (0)

Report
Copy link

Link copied!

I’ve been working on a package in Salesforce Loyalty Cloud for about 2 months inside a Loyalty Cloud org. Now I want to convert it into a 2GP managed package.

Here’s what I did so far:

I created a Dev Hub and a Developer Edition org for the namespace.

I registered the namespace in the Dev Hub.

I tried to create a managed package and version with the following commands:

Was this reply helpful? Yes No
CU27090804-0 on at

Like (0)

Report
Copy link

Link copied!

I’ve been working on a package in Salesforce Loyalty Cloud for about 2 months inside a Loyalty Cloud org. Now I want to convert it into a 2GP managed package.

Here’s what I did so far:

I created a Dev Hub and a Developer Edition org for the namespace.

I registered the namespace in the Dev Hub.

I tried to create a managed package and version with the following commands:

Was this reply helpful? Yes No
CU27090804-0 on at

Like (0)

Report
Copy link

Link copied!

How to create a managed package that depends on Salesforce Loyalty Cloud objects

Was this reply helpful? Yes No
CU27090804-0 on at

Like (0)

Report
Copy link

Link copied!

How to create a managed package that depends on Salesforce Loyalty Cloud objects?

Was this reply helpful? Yes No
Suggested answer

CU27090804-0 on at

Like (0)

Report
Copy link

Link copied!

I’ve been working on a package in Salesforce Loyalty Cloud for about 2 months inside a Loyalty Cloud org. Now I want to convert it into a 2GP managed package.

Here’s what I did so far:

I created a Dev Hub and a Developer Edition org for the namespace.

I registered the namespace in the Dev Hub.

I tried to create a managed package and version with the following commands:

1 people found this reply helpful.

Was this reply helpful? Yes No