-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quarantined App - Governance CoE - able to track users that tried to use the app while in quarantine #6130
Comments
We do not have this authored but it could be done by cross referencing the audit logs. |
Thanks, Jenefer! I assume there still won't be a trigger that would alert the user if they are accessing the quarantined app in real time, correct? I assume you might query the Audit logs and keep track of the users that accessed a quarantined app and present a report at a particular schedule? Would like to listen more to your thoughts. |
Thanks, Manuela! This helps, appreciate your feedback. |
Re-opening so it gets closed as part of our August release and shows up in the Release notes :) |
@alzia-msft This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us. |
Does this question already exist in our backlog?
What is your question?
In Power Platform CoE Governance module, if an app is quarantined, I want to send the users subscribed to the app when they access it that the app is quarantined and cannot be accessed. Can this be created in a Flow or possibly in the existing Admin | Set app quarantine status & Admin | Quarantine non-compliant apps Flows?
What solution are you experiencing the issue with?
Governance
What solution version are you using?
Latest
What app or flow are you having the issue with?
No response
What method are you using to get inventory and telemetry?
Cloud flows
The text was updated successfully, but these errors were encountered: