Patient outreach deployment: Best practices and considerations
Important
Effective January 30, 2025, the patient outreach solution (outbound marketing and journeys) will be retired and no longer supported.
Have questions? Reach out to us at Microsoft Cloud for Healthcare.
These deployment best practices and considerations for deploying patient outreach to support the pillars of Well-Architected for Microsoft Cloud for Healthcare.
Note
Dynamics 365 Marketing and Dynamics 365 Customer Insights are now Customer Insights - Journeys and Customer Insights - Data. For more information, see Dynamics 365 Customer Insights FAQs
New Customer Insights - Journeys customers receive real-time journeys features only. For more information, see Default real-time journeys installation.
Configuration
Dynamics 365 solution deployments perform a write lock on your environment to prevent parallel deployments of solutions.
Microsoft Cloud Solution Center displays limited logs and telemetry data during the deployment in case anything fails. Make 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.
You can select add sample data when deploying the solution via Solution Center.
If you're deploying to an Environment in Power Platform that previously had the Marketing solution deployed, then the Service support admin must use the same user ID as was used for the initial install. If not, a user with Power Platform Admin or Dynamics 365 Admin permissions must deploy it.
To deploy the patient outreach solution, the user must have an assigned license for the Healthcare add-on.
Ensure appropriate RBAC (role-based access control) is assigned to the security group for the dedicated environment for healthcare in Power Platform. Ideally, you should assign these roles as part of the environment creation process.
If privileged access to application registration in Microsoft Entra ID can't be granted for the group/users deploying the Dynamics 365 Marketing solution and patient outreach scenario, a Global Administrator must assist with the deployment.
Important
Microsoft recommends that you use roles with the fewest permissions. This approach helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role.
Use segment-based journeys to create groups of related contacts that you can target with patient journeys.
Use dynamic or static segments based on your scenario. Dynamic segments allow you to define a group based on set of rules or conditions. Static segments are populated by adding contacts explicitly.
Use trigger-based patient journeys when you want to react to patients' actions faster with personalized content.
Use real-time marketing as is the most up-to-date version of Customer Insights - Journeys.
If administrator permissions are needed to complete the deployment, ensure there's a joint activity to troubleshoot and follow-up with support in case Dynamics 365 Marketing deployment is having issues.
Deploy Dynamics 365 Marketing (Customer Insights - Journeys) to the development, test, and production environment to align with the overall environment strategy recommendations for Industry solutions in Power Platform.
Deploy patient outreach to test, development, and production environments similarly following Dynamics 365 Marketing (Customer Insights - Journeys) recommendations.
The following aspects are related to domain configuration:
Customer Insights - Journeys supports most of the Dynamics 365 platform's application lifecycle management capabilities but make sure to check the difference in specifics of some common pitfalls.
Use email A/B testing to find out which of the two similar designs is likely to be the most successful.
- When you replace version A with version B, version A is permanently deleted, and you can't undo this action.