Share
Report
5,133We have implemented Azure Blob Storage for our solution and are currently facing an issue with Azure Blob Storage access in the sandbox environment of a specific tenant.
The issue is not related to our customizations, as we removed all customization extensions and tested the standard environment. However, the issue still occurs for this particular tenant.
We performed the following tests:
- Azure Blob Storage works correctly in the production environment of the affected tenant.
- The same functionality works correctly in both production and sandbox environments of another tenant.
- Restoring a backup from the affected production environment into a sandbox environment does not resolve the issue.
- However, when we create a fresh environment within the same tenant and restore the same backup into that new environment, Azure Blob Storage works correctly.
Based on these results, we suspect that the issue may be related to an environment-level or tenant-specific configuration, permission, authentication setting, or restriction related to accessing external services from the sandbox environment.
We would like to know:
- Is there any specific configuration or permission required to allow a sandbox environment to access Azure Blob Storage or external file services?
- Are there any tenant-level or environment-level settings that could cause this behavior?
- Could restoring a production backup into an existing sandbox environment retain any configuration that might prevent access to Azure Blob Storage?
- Are there any recommended checks or troubleshooting steps for the following integration flow?
External File Service → Azure Blob Storage
Any guidance or suggestions would be greatly appreciated.
All responses (
Answers (
