The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
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
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
If you are creating background automation with Microsoft Flow that is using the Common Data Service (CDS) connector triggers or actions as part of an overall solution you should consider using service principles on the connection instead of having it tied to a specific user account. This allows you to configure the minimal permissions required by the flow and ensures the flow actions are not tied to a specific human user.
Service principles are created by registering an Azure AD application and then creating a corresponding application user in CDS. Application users are a special type of non-interactive user records in CDS. When you use an application user/service principal on the CDS connector all actions are performed by that user. Application users get the permissions from the security roles associated with the CDS app user. This allows you to define very specific rights to what the flow can do. All application users are created with a non-interactive user account, however, they are not counted towards the five non-interactive user accounts limit. In addition, there is no limit on how many application users you can create in a CDS environment.
To configure a service principal on the CDS Connector, you must complete the following steps
1) Register the Azure Active Directory Application and create a client secret ( Walkthrough from Docs )
2) Create an App User in CDS and Assign a security role (Walkthrough from Docs )
3) Configure your CDS Connection for a service principal using the information you just configured
Business Applications communities