Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Microsoft Power Automate provides users the ability to quickly create and integrate applications within the enterprise. With this ability comes concerns with governance to ensure users are allowed the appropriate permissions as well as identifying specific connections created and shared across the organization. Power Automate Flows offer a wide array of connectors and the ability to identify which of these are used and the connections created is essential to applying security policies to the Power Platform.
This article will build off of Power Automate - Auditing and Activity Logs Part 1 to examine how to search and store audit and activity logs for Power Automate. This includes how to turn on auditing, how to use the Office 365 Compliance Portal, the Unified Audit Log PowerShell command and the Office 365 Management Activity API. We will conclude with thoughts on monitoring tools such as Azure Sentinel, and storage tools such as Cosmos DB and Azure Blob Storage.
Searching the Unified Audit Log can be performed both manually and with automation. Manually there is a portal called the Office 365 Security and Compliance Center Portal that provides a centralized area for auditing all Office 365 services including the Power Platform. If automation is desired the Unified Audit Log offers both a PowerShell module and an API which can be subscribed to. This section covers all three of these in detail.
To begin using the Office 365 Unified Audit Log, your organization will need to have at minimum a specific Office 365 or Microsoft 365 license. Currently the license if the E3 license. The type of license will impact the retention of the logs, E3 is for 90 days while the E5 license retains for a year by default. To turn on, click the "Turn on auditing" button. If an error message occurs, most likely its due to licensing.
Users will need to be an Office 365 Global Administrator or be a member of one or more Security and Compliance Center role groups. To provide a user access to the Security and Compliance Center, use the Office 365 Admin Center and open the Admin center for Compliance. Alternatively, you can directly access the permissions page from here. The permission needed is "View-Only Audit Logs" or "Audit Logs" which allows for viewing and exporting of audit reports.
The Office 365 Security and Compliance Center found at https://protection.office.com can be used by security analysts to manually search for specific events using a portal user interface.
As shown in the image above, a single action or multiple activities for Power Automate can be chosen for analysis. To begin our search, run an audit log search by specifying the activities, the time range and optional search parameters such as users or site. Once the search is complete, review the results in the portal. The results are maxed out at the most 5000 newest events and are incremented 150 records at a time.
Below is an image showing a drill down into the Edited Flow audit record.
Below is an image showing a drill down into the Put Permission audit record.
In Part 1 we discussed the concept of Solution Aware Flows which are packaged within a Common Data Service solution. This section will investigate the creation of the solution aware flow as it is shown in both the Office 365 Security and Compliance Portal as well as the record within the Common Data Service.
When creating the flow within the solution we are invoking both the Power Automate audit logs as well as Common Data Service or Dynamics 365 audit logs. By combining both in the Office 365 Compliance Portal, an admin can visualize the flow that takes place.
Consider the images below.
The image above shows the initial addition of the flow to the solution as highlighted by the red box. The image below shows a combination of Dynamics and Power Automate audit records.
This shows from Dynamics 365 the SetState and ExecuteTransaction logs (more on this in the Model Driven Audit Log article!) as well as the Created Flow event from Power Automate.
Reviewing this we can see the a SetState operation happens at 06:32:27 before the Created flow event at 06:32:29. To set the state of a record, one needs to be created which can be confirmed using the Dynamics 365 / Common Data Service API.
To begin our search the Common Data Service API, let's review the Created Flow event.
Now to review this flow within the Common Data Service, a new browser or web request can be made with the Common Data Service API call similar to the following:
"https://.crm.dynamics.com/api/data/v9.0/workflows?$filter=workflowidunique eq "
This returns the following Common Data Service record.
From this image we can see the created on field in Common Data Service fits within our audit log timeframe and includes the correlation between the Power Automate flow name and Common Data Service workflowidunique field. In a follow up article we will explore this deeper when discussing solution aware components.
For PowerShell the Search-UnifiedAuditLog, part of the Exchange Online PowerShell V2 module, is used for Office 365 services including Power Automate. For Power Automate there exist a record type called "MicrosoftFlow" that will scope to only logs from Power Automate. Using the same table above, here are the PowerShell Operation equivalents to each captured event:
To use the Search-UnifiedAuditLog, connect using the Connect-ExchangeOnline cmdlet. This is a replacement for using the New-PSSession, however currently creating this session will also work.
$UserCredential = Get-Credential
Connect-ExchangeOnline -Credential $UserCredential
NOTE: Please refer to the section "Important Notes on the Exchange Online Module" for important authentication considerations.
The below PowerShell command uses the Search-UnifiedAuditLog to search for any activities related to Canvas Apps. To specify this, use the -RecordType argument with the value "MicrosoftFlow".
$endDate = Get-Date
$startDate = $endDate.AddDays(-7) #Search last 7 days
Search-UnifiedAuditLog -StartDate $startDate -EndDate $endDate -RecordType MicrosoftFlow
As the image above shows, this will bring back all activities related to Power Automate. Depending on what type of audit record you're looking for, the search can be filtered using the Operation argument.
Example of searching for Power Automate creation events:
Search-UnifiedAuditLog -StartDate $startDate -EndDate $endDate -RecordType MicrosoftFlow -Operation "CreateFlow"
Here is an example searching for a known user who has created flows:
Search-UnifiedAuditLog -StartDate $startDate -EndDate $endDate -RecordType MicrosoftFlow -Operations "CreateFlow" -UserIds 'firstname.lastname@example.org'
Each record returned includes the data of the audit, the user and the data collected within the AuditData property. The flow and environment properties are available within this property which can be extracted and stored for contextual information to a log data store. For help working with the AuditData property, consider using with the "ConvertFrom-Json" cmdlet.
$AuditData = ConvertFrom-Json -InputObject $_.AuditData
Azure Automation allows for the use of running PowerShell runbooks in Azure. Here is an example image of the output from running the Search-UnifiedAuditLog in Azure Automation:
One of the benefits of Azure Automation is the ability to schedule the execution of our script. The image below shows the recurrence based on a schedule created.
Another benefit is the native integration with Azure Log Analytics. This integration will come in handy further in this article.
Kusto Query for Log Analytics:
| where StreamType_s == "Output"
| project TimeGenerated, ResultDescription
NOTE: I want to point out verbiage that exists on the Search-UnifiedAuditLog page referring to programmatically downloading data from the audit log:
If you want to programmatically download data from the Office 365 Audit Log, we recommend that you use the Office 365 Management Activity API instead of using the Search-UnifiedAuditLog cmdlet in a PowerShell script. The Office 365 Management Activity API is a REST web service that you can use to develop operations, security, and compliance monitoring solutions for your organization. For more information, see Office 365 Management Activity API reference.
The above is important to point out that the current Exchange Online modules rely on Basic authentication. This is a major concern as it requires either a user to interactively login or to supply credentials as a username and password stored somewhere like Azure Key Vault.
Another way to automate delivery of audit data is by use of the Office 365 Management Activity API. To being using the API, an App Registration needs to be created in Azure Active Directory. The App Registration will need to have permissions to the Office 365 Management APIs, scoped to the ActivityFeed.Read permission. Once created, the App Registration can be used to get an access token for working with the API subscriptions and blobs. The below image shows the authentication flow and a single request to the API.
Now that the authentication mechanism is in place, we will have to tell the Office 365 Management API which activities we are interested in. This, in my opinion, is where I hope to see the API achieve filter parity with the PowerShell or Portal for the Unified Audit Log. For Power Apps Canvas Apps, there is no way to filter to the specific workload like what is available in the Portal or through PowerShell. This means we have to subscribe to a general bucket of events called Audit.General.
To get the authorization token and create the subscription I used Postman. I've included my sample Postman collection here which shows how to get an authorization token, to start a subscription, as well as poll for notifications.
As stated in the documentation, a subscription needs to be created for Audit.General. Each tenant you intend to monitor will need its own subscription. Once created, the subscription can be used to poll for events or as a webhook to have notification delivered when events are ready. NOTE: Subscriptions can take up to 12 hours before the content blobs are available.
For the webhook I followed a really great article by Amreek Singh that covers how to setup a subscription and webhook to deliver to Cosmos DB for storing and analysis. Included in his article are Power Automate flow examples that can be used to learn more. The example does not include the authorization token and I'm including this as an addition to his flows.
When receiving a notification, an array of content blobs will be delivered. Here's an example of a content blob notification:
Utilizing Azure Log Analytics or Azure Application Insights offers native integration with additional monitoring tools to help detect anomalies. Tools such as Azure Sentinel, offering a Security Information Event Management (SIEM) and Security Orchestration Automated Response (SOAR), or Azure Monitoring, offering analysis detection solutions, are perfect for this.
As stated above, based on the license type, audit logs are retained from 90 days to one year. However, business requirements may dictate a long term solution that could cover multiple years of audit activity. Regardless which mechanism to extract data, be it from the Portal or through PowerShell or the API, archiving these audits is a key requirement for most organizations. Each of these tools provide us capabilities to integrate these logs into a centralized data store such as Azure Blob Storage or Cosmos DB for long term retention.
This topic has a considerable amount of impact in your organization's strategy. A future article will cover this topic in more detail, and when published, I'll link from here.
A recent addition to the compliance tooling within Office 365 is the Advanced Audit feature. Currently I do not see anything specific to the Power Platform but this may change in the future. The key call out I see from the documentation is the ability to retain audit logs from one year and the high bandwidth accessibility for the Office 365 Management Activity API.
The other call out, is the throttling which is capped at 2,000 requests per minute.
In this article we have covered the Unified Audit Logs and what activities are currently captured for Power Apps Canvas Apps. Discussed were techniques to view the audit logs within the Office 365 Security and Compliance Portal as well as automated techniques using subscriptions and webhooks as well as automating PowerShell using Azure Automation. Consider the combination of using the Unified Audit Log to notify of events happening and the Power App Administration cmdlets to apply security and enrich audits from the audit log.
This article is designed to supplement the article on Power App Analytics, which provides more of an all up view of Canvas App usage. Combining these two documents, an administrator can now track analytic metrics as well as the events that define those metrics.
If you are interested in learning more about specialized guidance and training for monitoring or other areas of the Power Platform, which includes a monitoring workshop, please contact your Technical Account Manager or Microsoft representative for further details.
Your feedback is extremely valuable so please leave a comment below and I'll be happy to help where I can! Also, if you find any inconsistencies, omissions or have suggestions, please go here to submit a new issue.
Monitoring the Power Platform: Introduction and Index
Business Applications communities