Book Image

Fundamentals of CRM with Dynamics 365 and Power Platform

By : Nicolae Tarla
Book Image

Fundamentals of CRM with Dynamics 365 and Power Platform

By: Nicolae Tarla

Overview of this book

Microsoft Dynamics 365 provides a vast array of tools and applications to meet various Customer Engagement requirements. This Customer Relationship Management (CRM) guide covers the latest advancements in Dynamics 365 and Power Platform that help organizations adapt to changing market conditions for agility and resilience. With this book, you'll explore the core platform functionality of Dynamics 365 and explore its wide range of components for transforming your business with new services and capabilities. You’ll learn the basics of configuration and customization to enhance the functionality of Microsoft Dynamics 365 CRM and create solutions and custom applications by leveraging features such as apps, portals, automation, and business intelligence. As you advance, you’ll understand how Power Platform drives Dynamics 365 and how various integration capabilities add value by providing a comprehensive view of data aggregated across different systems and data sources. Finally, you’ll delve into core administration concepts that will help you to manage extensions added to the platform. By the end of this book, you’ll have learned how to tailor Microsoft Dynamics 365 to fit your organization’s requirements and tweak the platform to meet your business needs.
Table of Contents (20 chapters)
1
Section 1 - Platform Structure and Extensibility Capabilities
4
Section 2 - Default Modules Available with the Platform
10
Section 3 - Customization, Configuration, and Extensibility
14
Section 4 - Integrations
17
Section 5 - Administration

Configuring a domain name for your environment

One of the setup steps available with an Office 365 instance is the ability to configure a domain name associated with your instance. While you can continue working with Dynamics 365 for Sales without setting up a domain, it is a good idea to do it now. With the domain setup, you have one less configuration step to take before turning your trial into a production instance. In order to provide a better user experience, you should always configure your domain before going to production.

If you want to proceed with setting up a domain, you can either use an existing domain that you own or, for a few dollars, you can purchase a domain from various registrars. For the purpose of this book, I have purchased a .info domain from GoDaddy at https://godaddy.com/.

Let's look at the steps to configure a domain, as follows:

  1. Access the Office 365 admin center by navigating to https://portal.office.com/.
  2. You will be prompted to log in. Use the previously created account; this will get you to the main admin center console:
If you do not see the updated interface for the Office 365 Admin Center, look for a Try the Preview switch close to the top-right side of the page. Most likely, by the time you read this book, this will be the new interface standard. If you only see a subset of available options on the left navigation, click on the Show all option at the bottom. This will expand the listing of configurations.
  1. Next, expand Setup and select Domains. Here, you have the option to purchase a domain (if you haven't already done so) or just add a new domain:
For the purpose of this trial, I am assuming that you have already purchased a domain and you are just configuring it. If you choose not to use a domain, you can skip to the next section while using the default configuration.
  1. Go to Add domain. This will take you to the first page of the domain configuration wizard. This first page displays a nice process flow at the top, showing the stages that you have to pass through to configure your new domain and collecting the domain details that you intend to use with your instance:
  1. Follow the wizard to complete the domain configuration. When it is done, in the administration console you will have the ability to grant your users the ability to use the added domain instead of the default @[orgName].onmicrosoft.com account names. Now it all looks much more professional, and you have one less step to configure when you decide to turn this into a production instance.

Let's have a look at the Office 365 services that are available to be configured and integrated with our platform.