Deploy Microsoft Cloud for Financial Services solutions powered by Dynamics 365

Organization administrators can use this article to deploy Microsoft Cloud for Financial Services solutions powered by Microsoft Dynamics 365. At the end of this deployment process, you'll have one or more of the following financial services solutions or apps installed in your environment:

During the deployment process, you can configure more capabilities.

For information about the regions and languages available, see International availability of Microsoft Cloud for Financial Services.

Prerequisites

  • You must be a Microsoft Power Platform admin or a tenant admin to deploy the Microsoft Cloud for Financial Services solutions powered by Dynamics 365.
  • You must have licenses for Microsoft Cloud for Financial Services and various Dynamics 365 apps, which depends on the solution to be deployed. If you're missing any licenses, you'll be notified during the deployment process. More information: Licensing
  • Learn more in Compliance in Microsoft Cloud for Financial Services and ensure you use services that match your requirements.

Step 1: Prepare environment

To deploy financial services solutions, you need a Dataverse environment with a database. Although it's possible to create a Dataverse environment when you deploy a financial services solution, we recommend that your environment is ready first, and that you've installed the prerequisite Dynamics 365 apps and features.

  1. Sign in to Power Platform admin center.
  2. If you don't already have a Dataverse environment where you want to install financial services solutions, create a Dataverse environment with a database.
  3. When setting up your Dataverse environment, you must select Yes for Enable Dynamics 365 apps, there is no requirement to install any specific Dynamic app, however they must be enabled so a CE environment is setup.
  4. Open your new environment: go to https://[myenv].crm.dynamics.com, where [myenv] is the name of your environment.
  5. Install any dependencies for the financial services solutions and capabilities that you want to deploy.

Solution dependencies

Solution Dependencies
Unified customer profile Power Apps
Dynamics 365 Customer Insights
Customer onboarding - Loan onboarding Power Apps
Customer onboarding - Onboarding application Power Apps
Power Automate
AI Builder
Banking customer engagement - Intelligent apppointments Power Apps
Exchange
Teams

Note

The retail banking data model is a standalone option for partners and Dataverse customers. It is already included in Microsoft Cloud for Financial Services.

Important

The financial services data model has its own deployment process. For more information about deploying the financial services data model, go to Deploy the financial services data model (optional).

Step 2: Deploy financial services solutions

  1. Sign in to Microsoft Cloud Solution Center. In addition to using the preceding link, here are a few other ways to go there:

    • Select the link in the email you received from Microsoft after buying the Microsoft Cloud for Financial Services license.
    • From the Microsoft 365 admin center, select the Financial Services collection under setup and the action called Enable financial services solutions powered by Dynamics 365.

    Note

    If you need help, select Support in the left pane to open the Help + Support experience in the Power Platform admin center and get self-help solutions in real time.

  2. On the Home page, select the Microsoft Cloud for Financial Services tile to get started with the deployment, or select Solutions > Financial Services in the left pane.

    Select Financial Services on the Solution Center Home page.

  3. On the Solutions page, you'll see a list of available solutions to deploy.

    Review the available solutions in Microsoft Cloud for Financial Services.

    For each solution on the page, you can:

    • Select Quick view to learn more about the component and its dependencies.
    • Select the solution, and then select Add on the solution tile that appears. To include all solutions, select Add all Financial Services solutions.
  4. After selecting the solutions you want, select Deploy in the upper-right corner to deploy them.

  5. The Additional components page lets you install optional components for each solution you've selected.

    Note

    You'll see an option Configuration Data for each solution. If you're deploying the solution for the first time, select this option to enjoy an automated configuration process. If you don't select it, you'll have to configure the solution manually, or through FastTrack. At this time, no content is available to help you manually configure the solutions.

    However, if you have already deployed the solution with customizations and are performing an update, don't select the Configuration Data option—it will overwrite your customizations.

    If you deploy Unified customer profile, you'll see this:

    Install Unified customer profile dependencies.

    If you deploy Loan Onboarding, you'll see this:

    Install Customer Onboarding dependencies.

    Select Install or Configure for a dependency to view the documentation on how to set it up. Make sure you install the dependency in the same environment as the solution that depends on it.

    See Step 1 to review dependencies for each solution.

    If you deploy the Onboarding application, you'll see this:

    Onboarding application preview screen.

    a. Click Preview. b. Click Onboarding application (Preview). c. Click Add to deploy. d. Deploy the Onboarding application with or without the sample Onboarding application.

Onboarding application deployment screen.

  1. The Set up new deployment page lets you select the environment where you'll deploy the solutions.

    • If you've already prepared an environment, select it from the list.
    • Otherwise, select Create new to create an environment using the Power Platform admin center, and then come back to the Solution Center and select it. More information: Create an environment in the Power Platform admin center

    Select destination environment.

  2. Agree to the terms of service, and then select Next.

  3. The Configure dependencies page guides you to install and configure dependencies. The dependencies list will reflect the solutions you've selected to deploy.

  4. After you complete the dependency setup, return to the Microsoft Cloud Solution Center and select Recheck dependencies to refresh the Configure dependencies page.

  5. You now have the options to include sample content.

  6. After all the dependent apps have been installed and configured, and you selected any additional components, select Deploy to continue.

    Note

    The solution deployment starts and will continue to run in the background. Depending on the solutions you have selected to install, it might take a while for them to be deployed in your environment. You will receive a notification through email when the deployment has been completed successfully.

  7. After the deployment is complete, links will be available in the Microsoft Cloud Solution Center to launch your solution. There might be some extra steps to finish configuring your solution. Select the View documentation link to learn more about post-deployment configuration or explore our ecosystem for other financial services applications.

For information about post-deployment configuration for each solution, go to Post-deployment configurations for financial services solutions.

Note

If you are deploying Customer onboarding any custom document workflows are not activated and need to be configured. See post-deployment configuration guidance to activate the workflows.

Step 3: Add users and assign security role

To access the financial services apps you deployed, users in your organization must be assigned the appropriate security roles.

  1. Sign in to the Power Platform admin center.

  2. Select your environment by selecting the environment name, and then under Users select See all.

    Environment details to access users.

  3. On the Users page, add users to your environment and assign them the relevant roles.

    Also, depending on the solution you deployed, you'll have to assign additional security roles to your users so they can access the individual apps:

    Solution Security role
    Unified customer profile Basic user (or another core role with access to Power Platform)
    MC4FSI basic user
    Retail banking - contributor
    Relationship manager (be sure to allow the Relationship manager role access to Unified customer profile)
    Financial intelligence user (optional for Unified customer profile with Customer intelligence)
    Customer onboarding - Loan onboarding Basic user (or another core role with access to Power Platform)
    MC4FSI basic user
    Loan manager
    Customer onboarding - Onboarding application Basic user (or another core role with access to Power Platform)
    Onboarding agent (if deploying the application with no sample data)
    Sample Onboarding agent (if deploying the application with the sample Onboarding application)
    Banking customer engagement - Intelligent apppointments Basic user (or another core role with access to Power Platform)
    MC4FSI basic user
    Scheduling Admin and\or Scheduling Resource Manager (be sure to allow them access to Scheduling Administration app)
    Scheduling API user For users who test\trigger API
    Scheduling advisor - Advisor users do not necessarily need permissions to access the scheduling administration app, but do require mapping to this role to participate in meetings

Note

If you first deployed Dataverse and Unified customer profile, and then, in a separate installation, connected the Customer Insights for Dynamics 365 to the environment, the permissions initially created as part of the Financial intelligence user security role would not include the relevant tables generated by Customer Insights. Therefore, you should must validate permissions within the Financial intelligence user and make sure they are correctly mapped. This must include Read rights to the following tables:

msfsi_artifactmapping, msfsi_cimeasure, msfsi_cisegment, msfsi_ciprediction, msfsi_fsicimeasuresdatasource, msfsi_fsicipredictiondatasource, msfsi_fsicisegmentsdatasource, msdynci_alternatekey, msdynci_customermeasure, msdynci_customerprofile, msdynci_enrichment, msdynci_segmentmembership, msdynci_prediction, msdynci_unifiedactivity, msind_EntitytoCICustomerMapping, msind_Industrycimeasuredatasource, msind_Industrycipredictiondatasource, msind_industrycisegmentsdatasource, msind_industrymeasure, msind_industryprediction, msind_industrysegment, msind_industryunifiedactivity

Note

Users who access Unified customer profile without a role that allows editing rights on Contact records will see a message at the top of the application notification:

Read-only: You don't have access to edit this record.

With the above roles for Unified customer profile, users will be able to edit Life events, Relationships, and Groups. Add Contact editing rights to a user to remove this message.

See also

International availability of Microsoft Cloud for Financial Services
Post-deployment configuration for financial services solutions
Support for Microsoft Cloud for Financial Services
What is Microsoft Cloud for Financial Services?