Error message "Access Policies are missing" is displayed for api connections of logic app.

Hi ,

Thanks for reaching out to Microsoft Q&A.

The issue seems to be related to a few potential factors. Let me address them one by one:

"Access Policies are Missing" Warning:

• This warning generally means that the API connections do not have sufficient access to the underlying resources (e.g., storage accounts, SQL databases, etc.). Ensure that proper permissions (e.g., Managed Identity or Service Principal) are assigned to these resources.
  • You can resolve this by:

    - Verifying the API connection settings and re-authenticating the connection.
    
          - Checking the Azure resources to ensure the correct access policies or IAM roles are in place.
    
          **Intermittent Display of "Access Policies are Missing"**:
    
             - If the connections sometimes appear as "Connected" and other times as "Access Policies are Missing," it could indicate a transient or load-related issue with the Logic App gateway or Azure Portal's responsiveness. The connections might work during runtime but fail during a portal refresh due to throttling.
    
             **Error Code 429 ("Too Many Requests")**:
    
                - This error indicates that the Logic App or its API connections are hitting a rate limit. Azure services, such as Logic Apps, have thresholds for API connection calls. When exceeded, additional requests might be throttled.
    
                   - The **default threshold for Logic Apps Standard** depends on the SKU you are using, but typically, Standard Logic Apps can handle thousands of API requests per hour. Check the [Azure Logic Apps pricing documentation](https://azure.microsoft.com/en-us/pricing/details/logic-apps/) for exact thresholds.
    
                   **Filesystem-38 Specific Error**:
    
                      - The error in the second screenshot suggests that the **DMTS API** or its underlying system might be causing the problem (e.g., throttling at the source system or incorrect configuration in the connection).
    
                         - Steps to debug:
    
                               - Ensure the API connection's authentication credentials are valid and not expired.
    
                                     - Check if the DMTS API itself has a rate limit and whether it's being exceeded.
    
                                           - Try refreshing the connection or editing it in the portal.
    

Suggested Next Steps:

Check API Connection Settings:

• Go to each problematic connection, reauthenticate, and verify that access policies and permissions are set correctly for the underlying resource.

Review Throttling or Limits:

  - If rate limits are causing this issue, consider upgrading the Logic App or the DMTS API to higher SKUs to allow more throughput.
  
     - Introduce retry policies in your Logic App to handle 429 errors gracefully.
     
     **Use Diagnostics and Monitoring**:
     
        - Use "Diagnose and solve problems" in the Azure Portal for Logic Apps.
        
           - Enable Azure Monitor diagnostics for your Logic Apps and API connections to track failures and identify bottlenecks.
           
           **Optimize the Logic App Design**:
           
              - Reduce the number of API connections by reusing them where possible.
              
                 - Use fewer actions and simplify workflows to avoid hitting thresholds.
                 

Please feel free to click the 'Upvote' (Thumbs-up) button and 'Accept as Answer'. This helps the community by allowing others with similar queries to easily find the solution.