Logic Apps Run History Inputs Outputs private Endpoint CORS

Question

We created a standard LogicApp with no public access. We now notice that we can no longer see the Run History Inputs Outputs and get the message below.

“Inputs and outputs are not loading due to the CORS policy

In order to see inputs and outputs you will need to add https://portal.azure.com to the allowed origins list in the API CORS settings. We can add this for you, but you may continue seeing the error for a few seconds while the backend updates.”

When we click [Add to CORS] it makes no difference. Enabling public access and adding our Public IP is not a preferred solution.

How have others overcome this so you can see the Run History Inputs Outputs?

Answer 1

The error you're experiencing with viewing the Run History Inputs and Outputs in a Logic App due to CORS (Cross-Origin Resource Sharing) policy is related to the security configurations and how Azure Portal interacts with the underlying services. Here are the steps you may consider taking to address the issue:

1. Verify CORS Settings in the Azure Portal

• Navigate to the Azure Portal and select the Logic App.
• In the Logic App blade, go to the "API settings" or "CORS" section.
• Verify that https://portal.azure.com is listed in the allowed origins. If it is not, manually add it.

2. Use Azure Resource Manager (ARM) Templates

• If the Azure Portal's UI is not reflecting the changes, consider using Azure Resource Manager (ARM) templates to configure CORS settings.

3. Clear Browser Cache or Try a Different Browser

• Sometimes, cached data in the browser can cause issues with updates in the Azure Portal. Clearing the browser cache or trying a different browser may resolve the issue.

4. Review Network Configuration

• Check your network configuration to ensure that no firewall or proxy settings are interfering with the communication between the Azure Portal and the Logic App.

5. Consider Contacting Azure Support

• If the issue persists, and none of the above steps resolves it, you may want to open a support ticket with Azure Support. They can investigate the specific details of your configuration and environment.

6. Monitor Azure Logic Apps with Azure Monitor

• As a temporary workaround, you can use Azure Monitor to view the logs and metrics for your Logic App. This won't give you the exact same view as the Run History Inputs and Outputs, but it may provide the necessary insights while the CORS issue is being resolved.

Conclusion

The CORS policy issue you're encountering is a known challenge, and typically it should be resolvable by adding the Azure Portal URL to the allowed origins list. However, certain network configurations, cache issues, or platform-specific nuances might necessitate the additional steps outlined above. If the issue remains unresolved, contacting Azure Support directly would be the advisable course of action, as they will have the necessary access and tools to diagnose and fix the problem.

Answer 2

Hello, @dobxml-0229 - Are you still blocked with this? If adding your Public IP like in this thread isn't preferred, you might be able to connect via VPN - is it something that you've explored?