How do I grant my users access to logic apps logging?
Give business users and operators self-service logging for your Azure Logic Apps. With a Role-based Log View, they find business transactions by Order Number or Customer ID on their own, without Azure Portal access and without asking the integration team.
- ✅ Search Logic Apps transactions by business data with Search Fields
- ✅ No Azure Portal access needed for business Users
- ✅ Fine-grained, Role-based access per Log View
- ✅ Correlate events across Logic Apps using the RunId
This guide shows how to configure Nodinite to display logged data from your Azure Logic Apps (see Logging Logic Apps) and let responsible users gain role-based access using a Log View.
Info
This guide assumes you have already installed the agent (Install) and that you have Logic Apps with diagnostic settings configured in at least 1 Azure subscription (Prerequisites - Logic Apps, Configuration - Logging).
Example #1: Hello Logic Apps Logging
This step-by-step guide shows how to provide self-service logging access for your users. It also explains Log Views access and logging access for Azure Logic Apps business transactions.
Info
You must be assigned the Administrators Role to perform the steps below.
Step 1: Configure Message Types
First, configure Message Types to identify your business transactions, for example PurchaseOrder, Invoice, and Shipment.
Step 2: Configure Search Fields
Configure Search Fields with Search Field Expressions to extract business identifiers such as Order Numbers, Customer IDs, and Invoice amounts.
Step 3: Create a Log View
Follow the steps in Add or manage Log View to:
- Create and name the Log View.
- Assign user rights via Roles.
- Select the Log Agent configuration that corresponds to your Azure Logic Apps Logging and Monitoring agent (Overview).
- Configure filters and Search Fields.
- Save the Log View.
Your Logic Apps Log Events appear in the Log View for authorized users. To group the events of each run, see Design grouped Log Views for Runtime Inspection.
Info
Users assigned to the Log View can search by business data such as Order ID and Customer ID without Azure Portal access.
Step 4: Search and Filter Log Events
Users can now:
- Search by business identifiers using Search Fields.
- Filter by Log Status Codes to find failed runs.
- View full payloads for detailed troubleshooting.
- Correlate events across Logic Apps using the RunId.
Example of a Log View where a user finds a failed Action by its Log Status Code.
How do I grant my users access to Logic Apps Monitoring?
The User access to logic apps monitoring guide details this topic.
Next Steps
- Articles - Operator instructions (knowledgebase).
- Repository Model - Documentation with Custom Metadata for more informational alerts.
- User access to logic apps monitoring