Care Management Deploy Best Practices and Considerations

In this guide, we will explore the best practices and key considerations for deploying Care management application capabilities.

  • You will need to have Power Platform admin or a tenant admin to deploy the Microsoft Cloud for Healthcare solutions powered by Dynamics 365.
  • You must have licenses for Power apps, which depends on the solution to be deployed. If you're missing any licenses, you'll be notified during the deployment process. If new licenses are needed for deployment, please wait about 8 hours after purchasing for the system to be ready for set-up.
  • After you acquire a license, you need to wait for the system to be ready for setting up. Check Microsoft Cloud Solution Center for details.
  • Dynamics 365 solution deployments put a write lock on your environment to prevent parallel deployments.
  • When setting up your Dataverse environment, you must select Yes for Enable Dynamics 365 apps. Although you need not install any specific Dynamics app, you must enable the option so that a CE environment is set up.
  • You will do the deployment from the solution center.
  • Sample data can be added when deploying the solution in the solution center, however you cannot remove the sample data from solution center.
  • Microsoft Cloud Solution Center has limited logs and telemetry available during the deployment in case anything fails. Be sure to reserve enough time to install the applications successfully. To view the deployment status of your solutions, go to your environment in the Microsoft Power Platform admin center. For more information, visit Manage Dynamics 365 apps.
  • If you're deploying the solution for the first time, select the "Configuration Data" option to enjoy an automated configuration process otherwise you will need to do the post deployment configuration as a post-deployment step.
  • If you have already deployed the solution with customizations and are performing an update, don't select the "Configuration Data" option as it will overwrite your customizations.
  • The solutions in Microsoft Cloud for Healthcare are not multi-geo by design. If data processing laws require that data be preserved in the country/region, a deployment tenant must be created in the geography to ensure that data stored in the services stay within the region. Check out the regions and languages supported.
  • Deployment of D365 solution can take several hours and puts a write lock on the environment to prevent parallel deployments of solutions.
  • There's limited logs and telemetry available during the deployment in case anything fails, hence you should ensure you have reserved enough time to get the D365 app installed successfully as a dependency to the unified customer profile solution deployment. You will receive a notification through email when the deployment has been completed successfully.
  • If you enable the Teams collaboration and chat feature from Microsoft Care Management app or a custom app, it's enabled for all the supported apps.

Next steps