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
We normally move all of our changes through the solutions. But we have a requirement so that we want to create a new security role in the production directly with the name 'abc'. But we are not going to create the same security role in any of our lower environment.
Is it the right approach? Do you think that this gonna create any problem in the future for the solution deployment?
Amit Kumar Rath
It is always recommended to carry all your customizations including security roles via solution packages as you were already doing it. It is difficult to comment on what challenges you would have going forward. I wonder what is the challenge this time around for not following the best practices! Making direct modifications causing unmanaged customizations is never the right approach. Try to refrain from it as much as possible.
D365 Support Engineer
Business Applications communities