Insufficient permission to see Log Analytics logging step in Standard Logic App

Michal Pipal 25 Reputation points
2025-02-10T16:57:02.29+00:00

I have a Standard Logic App that uses the Azure Log Analytics Data Collector connector to send logs to Log Analytics (LA).

In the 'connections.json' definition, I am referencing most of the values from Environment Variables

{
    "managedApiConnections": {
        "azureloganalyticsdatacollector": {
            "api": {
                "id": "@appsetting('log_connection_api_id')"
            },
            "authentication": {
                "type": "ManagedServiceIdentity"
            },
            "connection": {
                "id": "@appsetting('log_connection_id')"
            },
            "connectionRuntimeUrl": "@appsetting('log_connection_runtime_url')"
        }
    }
}

I have the app deployed in multiple environments. On TST, I am the Owner of the application and when I open any run, I can see and investigate the logging step and its inputs
User's image

However, I am only a Reader and Monitoring Reader in the ACC and PRD environment. When I open the app, I see all the steps successfully except for the logging step. It is throwing an error that it is apparently not able to access Environment Variables somehow.

User's image

In the Network tab, I see this strange request done by Azure Designer.

User's image

I've tried to assign a Logic Apps Standard Reader (Preview) role, but it didn't help. It works when I assign myself either Logic Apps Standard Developer (Preview), Contributor, or Owner. But this also gives me a permission to modify the app, which I don't want.

Is there some role that allows me to see the run without issues and also restricts me from doing any modification to PRD apps? After all, I just want to see the app details, not modifying anything.

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,348 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,887 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Sai Prabhu Naveen Parimi 0 Reputation points Microsoft Vendor
    2025-02-11T21:50:52.79+00:00

    Hello Michal Pipal

    Since Logic Apps Standard Reader (Preview) already includes Microsoft.Web/sites/config/appsettings/read, but you're still unable to access the logging step, it might not be a missing permission issue but rather how log access is handled in your environment.

    You might need additional permissions like:

    • Microsoft.Insights/logProfiles/read – This allows access to log profiles.
    • Microsoft.OperationalInsights/workspaces/query/read – This grants permission to query Log Analytics workspaces.

    If your logs are being sent to Azure Monitor Log Analytics, you might need explicit access to the Log Analytics workspace itself. You can refer to this Microsoft document for details on managing Log Analytics workspace permissions: https://learn.microsoft.com/en-us/azure/azure-monitor/logs/manage-access?tabs=portal

    Could you check if you have the necessary permissions there? That might resolve the issue.

    0 comments No comments

  2. RithwikBojja 75 Reputation points Microsoft Vendor
    2025-02-13T06:34:11.3733333+00:00

    Hi @Michal Pipal,

    When you are giving Logic Apps Standard Reader (Preview) role, you will not be having privileges to read the Environment Variables, Parameters, Read/write app settings.

    Even Logic App Standard Operator (Preview) role, allows you to Trigger/resubmit runs but not access the variables.

    So, only option is that you have to use Logic App Standard Operator Developer or Contributor Role as it gives the Log Analytics connector to access the Variables.

    enter image description here

    Also refer this Microsoft-Tech-Blog by @WSilveira, which says the same.

    Hope this helps.

    If the answer is helpful, please click Accept Answer and kindly upvote it. If you have any further questions about this answer, please click Comment.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.