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
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
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
I've been told that MS have deprecated local portal user accounts for D365 portals, in the future all will be external accounts. They're still there today, but not sure how long this will be the case.
The thing is, I find local portal user accounts to be a very convenient way of testing behavior - I've previously created a number of dummy accounts, with dummy contacts holding different web roles. Its then trivial to log in with each dummy account to make sure the views and actions are the correct scope for each dummy user. What with GDPR and other regulations it's important to check the business isn't 'over sharing' the data within CRM.
Once local accounts are removed, i'm not sure how i'd achieve this as simply as i can now.
Anyone here do something similar and have thoughts on how best to approach portal testing with dummy data?
We also often use local accounts for testing because they are convenient. However, if you're using an external identity provider, it's not really that much harder to setup something similar. If you use Azure AD B2C, you can create dummy accounts on your favorite platform and use them on all of your implementations. You still get contacts for all of those accounts that you can associate web roles to for testing, so it's not much different. In fact, if you're dealing with different environments, sharing the dummy external accounts can save a bit of password management.
Also, while yes I've heard the same thing that they are going to be depreciated, I think it's probably still a while before that happens (and actually the note about depreciation isn't on the documentation anywhere). There are a lot of people who use them who would need to migrate. My best guess is this is years (not weeks or months) away from actually happening, or at least many, many months.
Hope that helps.
Just as a follow up, I was able to confirm that local authentication is definitely still deprecated, so it's best to get familiar with the other authentication providers, preferably Azure AD B2C.
We tried Azure AD B2C and found it to be terrible and largely undocumented. We use a different external provider. But yes, I guess we'd better get used to operating without local accounts
Business Applications communities