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 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 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
This is an extension to a post I seen that explained problems and solutions regarding individuals who are deleted from AD and then added back later and how certain values in the CRM Database tables need to be changed to match certain values from AD.
Follow to see the post
However what I would like to do is gain some further knowledge as far as what the function of each piece is.
If AD's ObjectGuid doesn't match the users SystemUserBase.ActiveDirectoryGuid It will prevent you from being able to activate said user. Is this the only function of the ActiveDirectoryGuid in the login process? Because, if you manually make the the ActiveDirectoryGuid match the record that the user is associated with in AD it allows you to activate them but in some cases the user will still be unable to log in due to a mismatch with the AD's SID and CRM's MSCRM_CONFIG.SystemUserAuthentication.AuthInfo.
Within the MSCRM_CONFIG.SystemUserAuthentication.AuthInfo you will normally see 2 records. One that contains the SID formated
While the other is formatted
Which leads into my next series of questions.
When does it use one record over the other, or does it require to have both records?
Does it only use SID if you are using an automated login process? (making it so that the user doesn't have to use any credentials)
Is the latter what is required for the user to type in as their UserName.
Can it be changed and subsequently what ever you changed it to be required to be used as the UserName during login?
I apologize for the badgering of questions here but I want to make sure I fully understand what each piece is doing so that I can develop a process to fix what ever issue comes up regarding this.
Business Applications communities