Microsoft Dynamics 365 | Integration, Dataverse...

403 Forbidden in Data Management

(0) Share

Report

Posted on by Henrik Marx Larsen Microsoft Employee

Has anybody come across this problem...?

When I try to download a package in Data Management, I receive the follow error: The remote server returned an error: (403) Forbidden.

I get something similar when I try to use the image upload button on a maintenance asset.

However, uploading images through document management works fine.

It would appear that my instance does not allow me to interact with local files in certain cases.

I am using a sandbox provisioned through PPAC. Interestingly, I have created a similar sandbox in a difference environment and that works fine.

I have attached a screenshot from Data Management.

Categories:

Dynamics 365 general

I have the same question (0)

All responses (8)

Answers (0)

Sort by

Suggested answer

Navneeth Nagrajan 2,568 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @HM-08041147-0,

A few questions:

1. Have you tried restarting the DMF services on the sandbox where this 403 error is showing up?

2. Has the storage link been setup or refreshed with respect to the blob storage connection (if any)?

Suggestions:
In the environment where the 403 error pops up try refreshing the environment from the PPAC Admin center -> Environments section. This enforces an internal storage token generation.

Check the linked storage account post refresh to verify the internal storage token. Under Data Management -> Framework parameters -> Entity Settings -> Refresh the entity list.

Had a similar issue and tried the above troubleshooting steps and it resolved the 403 Forbidden error (Blob storage access issue).

Hope this helps. Happy to answer questions, if any.

Was this reply helpful? Yes No
Henrik Marx Larsen Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Many thanks for your reply.

By refresh, I assume that you mean enabling / disabling maintenance mode for the environment...?

The entity list has been refreshed and the storage token validates in the framework parameters.

I am not sure the problem is limited to Data Management since I am also unable to upload files elsewhere. For instance, under Asset management / Assets / All assets / General / Image, I get an error when I try to upload an image for the asset.

It seems to be some security block for this particular instance.

I have another instance running in the a different environment that works fine. Weird...

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 303,986 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Henrik,

When you mentioned that it is working in a different environment, is this on the same tenant or another tenant? If this is not a production environment, you can try to copy another instance over this non-functioning environment or redeploy it. In some rare cases, the instances might not be configured correctly during deployment. E.g., I have one environment where virtual entities are not working at all.

Was this reply helpful? Yes No
Henrik Marx Larsen Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @André Arnaud de Calavon,

Hope you are well. Thanks for your reply.

Interestingly, the two environments (sandboxes) are within the same tenant and accessed through the same browser.

It is sandbox, but I am not keen on redeploying since I will lose a lot of work :(

Weirdly, if I upload an image on a record using document management, it works fine.

The problem originally occurred with V10.0.45 but went away with V10.0.46 and then came back with V10.0.47 so it seems the updates are changing some security settings or tokens. Just can't work out which...

I also had the virtual entities problem with V10.0.46 but it went away when I deployed V10.0.47... Strange.

Was this reply helpful? Yes No
André Arnaud de Cal... 303,986 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi Henrik,

Maybe you can try to create a new environment and then copy your current environment on top of the new one. Then check if the "lot of work" is in the new environment and this error is present in that new environment.

Was this reply helpful? Yes No
Navneeth Nagrajan 2,568 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Agree with Andre. You can either copy the environment to a different environment. Looks like Storage account token generation is broken in the environment.

Under this broken environment with 403 error, do you see an Application user in the Power Platform Admin center with the name "Data Integration Dynamics Data Integration" in Active state?

Was this reply helpful? Yes No
Henrik Marx Larsen Microsoft Employee on at

Like (2)

Report
Copy link

Link copied!

Great idea. I have started the copy, so let's see how that goes...

Was this reply helpful? Yes No
Henrik Marx Larsen Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

@André Arnaud de Calavon, I copied the environment and interestingly, the same problem occurs in the newly deployed instance of D365F&O. Therefore, the problem must relate to a security setting in the environment because it works in a cleanly installed environment. Interesting, but at least it isolates the problem...

Was this reply helpful? Yes No