A few weeks ago I saw a message in the M365 Message Center regarding “Non-compliant” flows. Unfortunately, I can’t find the message any longer, but it was pretty concerning because
All posts tagged in enforcement
6Articles
If you have custom applications built on Dynamics/Dataverse within the US Government Community Cloud (GCC) and only have Team user license that were purchased after October 2018 your apps screen
In my previous blog post I described how the naming convention for flows with a Common Data Service (current environment) trigger can be enforced with Power Automate flow, and could
Enforcement of naming convention on workflows can be Power Automated, as described in my previous blog post. This is also possible for Power Automate flows. The trigger parameters from the
Enforcement of the naming convention, as described in my previous blog post, can be Power Automated. The CDS|Dynamics 365 workflow properties (attributes value) can be used to compose the prefix
- 1
- 2
Top Headlines
Support The Site
