Azure Storage Networking Issue

We have an issue with opening our data after we moved from VM to managed service. The below is what AI says about the issue, is this something you can help with?

Regards

Simon

The log you provided is from an Azure DevOps pipeline deploying a multi-container application to Azure App Service. Here's a breakdown of the key steps and issues mentioned in the log:

Key Steps:
Starting the Deployment:

The deployment process starts for the Azure Web App on Container, named reproquodev.
Task Initialization:

The task used is Azure Web App for Containers (version 1.244.1) provided by Microsoft.
Service Connection:

The pipeline retrieves service connection details for the Azure App Service reproquodev.
Multi-Container Deployment:

The deployment process involves transforming a Docker-Compose file to deploy multiple containers to the web app.
Deprecation Warning:

A warning is issued about the deprecated Buffer() method in Node.js, suggesting the use of Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
Updating App Service Configuration:

The pipeline updates the configuration settings of the App Service with details from the Docker-Compose file.
Restarting the App Service:

The App Service reproquodev is restarted to apply the new configuration settings.
App Service Restarted:

The App Service restarts successfully.
Issue Encountered:
Error Updating Deployment History:
There is a warning indicating that the deployment history update failed with a 403 Forbidden error (Ip Forbidden). This typically means that the IP address making the request is not allowed to access the resource due to IP restrictions or firewall settings.
Application URL:
The deployed application can be accessed at https://reproquodev.azurewebsites.net.
Summary:
The deployment process starts and initializes correctly, retrieves the necessary service connection details, and performs a multi-container deployment using a Docker-Compose file.
The App Service configuration is updated, and the service is restarted successfully.
However, there is an issue with updating the deployment history due to an IP restriction, resulting in a 403 Forbidden error.
Recommendations:
Addressing the 403 Forbidden Error:

Review and update the IP restrictions or firewall settings on the Azure App Service to ensure that the IP address used by the Azure DevOps pipeline is allowed to access and update the deployment history.
Check the networking configuration, especially any IP restrictions under the "Networking" section in the Azure portal for the App Service.
Handling Deprecation Warnings:

Update the Node.js code to use the recommended Buffer methods to prevent future issues related to deprecated methods.
By addressing these issues, you can ensure a smoother deployment process and successful update of the deployment history.