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 already developed a portal for a client of ours and has gone live. However, recently the company has been bought out and would require an additional portal with exactly the same functionality but with different branding (logo/colours). The additional portal needs to be hosted on the existing Dynamics 365 instance.
I was wondering what's the best way around this? I am thinking of creating another CSS web file for this company and then somehow linking this across to the new portal website? Is this possible? I also assume that I will need to re-create all the web-pages again. However, can re-use web, entity forms, templates etc that has been developed from the previous portal..
Any advice would be greatly appreciated.
You can actually have multiple websites in your environment: docs.microsoft.com/.../websites
I don't really think you would be able to manage the DNS entries through code
There are a number of ways of approaching this.
You could have two separate parts of the same portal, as described here:
What's nice about that approach is that you could reuse web forms, entity forms, templates, etc.
As Oliver mentioned, you can setup a second portal. The downside is that you can't really reuse the web forms, entity forms, templates, etc. You could do an initial copy, but changes moving forward won't be kept in sync.
Business Applications communities