contact-centre, copilot-studio, Customer Experience, Customer-service, Uncategorized

Raising the bar for healthcare security: Dynamics 365 Contact Center achieves HITRUST certification

Raising the bar for healthcare security: Dynamics 365 Contact Center achieves HITRUST certification (Meeting the gold standard of security, privacy, and compliance for healthcare data protection).

Real-time User Journey: Secure Healthcare Interaction

This journey illustrates how HITRUST certification provides a secure foundation for handling Protected Health Information (PHI) during a patient interaction:

  1. Patient Authentication: A patient calls their healthcare provider to discuss sensitive lab results. The system recognizes the caller and prompts for secure multi-factor authentication.
  2. Verified Environment: The call is routed via the HITRUST-certified cloud infrastructure. Every layer of the data path—from the voice stream to the database—is governed by the stringent security controls required by the certification.
  3. Secure Information Access: The agent opens the patient’s record. Dynamics 365 uses Role-Based Access Control (RBAC) to ensure the agent only sees the specific health data necessary to answer the inquiry.
  4. AI-Assisted Resolution: Copilot provides a summary of the patient’s history. Because the platform is certified, the provider can confidently use AI to process PHI without the risk of data leakage or non-compliance.
  5. Audit Logging: Every action the agent takes and every piece of data accessed is recorded in a tamper-proof audit log, meeting the “measurable” security requirements of the HITRUST framework.
  6. Patient Peace of Mind: The interaction concludes with the patient knowing their medical and personal data was handled with the highest level of industry-standard security.

Step-by-Step: How to Leverage This Security for Healthcare

HITRUST is a platform-level certification, meaning Microsoft has already done the heavy lifting of securing the infrastructure. To leverage this for your healthcare organization, follow these steps:

  • Step 1: Verify Compliance Status

Visit the Microsoft Trust Center or the Service Trust Portal to download the HITRUST Letter of Certification for Dynamics 365 and the Microsoft Cloud for Healthcare.

  • Step 2: Configure Business Associate Agreements (BAA)

Ensure your organization has a signed BAA with Microsoft. This is a prerequisite for handling HIPAA/PHI data on any Microsoft cloud service.

  • Step 3: Enable Data Encryption

In the Power Platform Admin Center, verify that Customer-Managed Keys (CMK) are enabled if your specific compliance policy requires an extra layer of control over data encryption at rest.

  • Step 4: Set Up Data Loss Prevention (DLP)

Configure DLP policies in the Microsoft Purview compliance portal to prevent sensitive medical identifiers (like SSNs or Patient IDs) from being shared via insecure channels (e.g., standard email or external chats).

  • Step 5: Define Secure Agent Workspace

In Agent Experience Profiles, use “Field-level security” to mask sensitive health fields so they are only visible to authorized medical staff, not general support agents.

  • Step 6: Conduct a Compliance Audit

Use the Compliance Manager within Microsoft Purview to track your organization’s specific implementation of HITRUST controls against the Dynamics 365 environment.

Infographic: The HITRUST Certification Advantage

FeatureStandard HIPAA ComplianceHITRUST CSF Certification
VerificationSelf-attestation (High Risk).Third-party audited (Low Risk).
ScopeFocuses mostly on Privacy/Security.Comprehensive: Covers HIPAA, NIST, ISO, and more.
AI ReadinessOften restricted for PHI.AI-Native: Secured for Copilot and AI Agents.
Data ProtectionBasic encryption.Multi-layered: Includes advanced physical and logical security.
Trust LevelVariable.The “Gold Standard” for healthcare and insurance.

References

contact-centre, copilot-studio, Customer-service, Power Apps

Teams Phone extensibility for Dynamics 365 Contact Center generally available

Teams Phone extensibility for Dynamics 365 Contact Center generally available (The General Availability of the “Teams Phone integration,” allowing organizations to use their existing Teams Phone infrastructure to power the Dynamics 365 Contact Center).

Real-time User Journey

This journey illustrates how a customer service representative (CSR) uses the integrated Teams Phone experience:

  1. Incoming Call: A customer calls the company’s support line. Because the system is using Teams Phone Extensibility, the call is routed through Microsoft Teams infrastructure directly into the Dynamics 365 Agent Workspace.
  2. Contextual Notification: The CSR receives the call toast within Dynamics 365. Simultaneously, the system performs a “Dataverse lookup” and pops the customer’s profile (Screen Pop) based on the phone number.
  3. Collaborative Resolution: During the call, the CSR needs help from a subject matter expert (SME) who is not in the contact center. Using the Integrated Directory, the CSR sees the SME’s real-time Teams presence and initiates a consult.
  4. Seamless Transfer: The SME provides the answer. The CSR can then either pull the SME into a three-way conference or perform a “Blind/Consultative Transfer” to the SME, all without leaving the Dynamics interface.
  5. Post-Call Transcription: Once the call ends, the Teams-driven transcript and AI-generated summary are automatically saved to the customer’s timeline in Dynamics 365 for future reference.

Step-by-Step: How to Enable This Feature

To enable Teams Phone as the primary voice provider for the Contact Center, follow these steps:

  • Step 1: Prerequisites

Ensure you have the required licenses for Teams Phone and Dynamics 365 Contact Center. Your agents must be assigned to a Teams Phone resource account.

  • Step 2: Admin Center Configuration

Sign in to the Contact Center admin center. Navigate to Channels > Voice.

  • Step 3: Select Voice Provider

Click on Add Channel. When prompted for the “Voice Provider,” select Microsoft Teams.

  • Step 4: Connect Resource Accounts

The system will prompt you to link your Teams Resource Accounts (Phone Numbers/Auto Attendants). Select the numbers you wish to use for contact center routing.

  • Step 5: Configure Workstreams and Queues

Create a Voice Workstream. Under the routing settings, ensure the “Teams” channel is selected. Map your Teams users to the corresponding Dynamics 365 Queues.

  • Step 6: Update Agent Experience Profiles

Go to App Settings > Agent Experience Profiles. Ensure that the “Teams Call Controls” are enabled so agents can access mute, hold, and transfer buttons within the web browser.

Infographic: Teams Phone vs. Standard Voice Channel

FeatureStandard Voice (Azure/3rd Party)Teams Phone Extensibility (GA)
InfrastructureRequires ACS or separate SIP trunk.Uses existing Teams Phone setup.
DirectoryLimited to Contact Center users.Company-wide Teams Directory access.
CollaborationManual invite to external experts.Native Teams Consult & Transfer.
PresenceIsolated Presence.Unified Presence (Teams & Dynamics).
Cost EfficiencyPotential separate per-minute costs.Leverages existing Teams calling plans.

References

AI Foundry, architecture, contact-centre, copilot-studio, Customer-service

Automate intent discovery and resolution with Customer Intent Agent in Dynamics 365 Contact Centre

Automate intent discovery and resolution with Customer Intent Agent (A specialized AI agent that proactively identifies emerging customer needs and builds the necessary logic to resolve them).

Real-time User Journey

This journey highlights how the agent transitions from “Discovery” to “Resolution” without manual administrative work:

  1. Passive Discovery: The Customer Intent Agent continuously scans thousands of historical transcripts and real-time interactions across voice and chat.
  2. Pattern Identification: The AI identifies a new, rising trend: many customers are asking about “Loyalty Point Expiration” following a recent policy change—a category that didn’t exist in the current routing rules.
  3. Intent Proposal: The agent alerts the supervisor: “I’ve discovered a new intent: ‘Loyalty Inquiry.’ Would you like me to create a resolution path for this?”
  4. Autonomous Training: Upon approval, the agent automatically maps relevant phrases to this new intent and suggests the best knowledge articles or automated bot topics to address it.
  5. Closing the Loop: The next customer who asks, “When do my points vanish?” is immediately recognized by the new intent and routed to the correct automated resolution, bypassing the general “Other” queue.

Step-by-Step: How to Enable This Feature

The Customer Intent Agent is part of the Agentic Contact Center suite. Follow these steps to activate it:

  • Step 1: Admin Center Access

Sign in to the Contact Center admin center or Customer Service admin center.

  • Step 2: Access the Agent Hub

Navigate to Operations > Agent Hub. This is the centralized control center for all autonomous agents.

  • Step 3: Enable Intent Discovery

Locate the Customer Intent Agent card and select Manage. Toggle the Discovery setting to On. This allows the agent to begin analyzing historical and live data.

  • Step 4: Configure Data Sources

Specify which channels (Voice, Chat, Email) the agent should monitor. You can also point it toward specific historical timeframes (e.g., the last 30 days) to find recent trends.

  • Step 5: Set Approval Workflows

Choose between Semi-autonomous (the agent suggests new intents for your approval) or Fully autonomous (the agent creates and applies the intent logic automatically). Microsoft recommends Semi-autonomous for the first 30 days.

  • Step 6: Link to Copilot Studio

Ensure the agent is connected to your Copilot Studio environment so it can automatically suggest or create new bot topics based on the discovered intents.

Infographic: The Customer Intent Agent Lifecycle

FeatureTraditional Manual DiscoveryCustomer Intent Agent
SpeedWeekly or monthly manual audits.Real-time continuous monitoring.
AccuracySubject to human bias/sampling.Data-driven across 100% of transcripts.
ImplementationManual rule-building & bot training.Auto-suggests phrases and resolution paths.
ScalabilityHard to track multiple minor trends.Captures long-tail and emerging issues instantly.
OutcomeReactive updates to routing.Proactive optimization of the service journey.

References

AI Foundry, architecture, Azure Development, contact-centre, copilot-studio, Customer-service

Expanding SMS capabilities in Dynamics 365 Contact Center

Expanding SMS capabilities in Dynamics 365 Contact Center (Introducing deeper integration with Azure Communication Services and enhanced two-way messaging features).

Real-time User Journey

This journey highlights how a retail customer uses the enhanced SMS features for an order issue:

  1. Notification: A customer receives an automated SMS update: “Your order #789 has been delayed. Reply HELP to speak with an agent.”
  2. Customer Reply: The customer replies “HELP.” The Unified Routing engine identifies the customer based on their phone number in the CRM.
  3. Agent Interaction: The SMS conversation appears in the Agent Workspace. The agent sees the full history of automated notifications sent to this customer.
  4. Rich Media Exchange: The customer sends a photo via MMS showing a damaged product they received previously. The agent views this directly in the chat window.
  5. Proactive Resolution: The agent sends a link via SMS for the customer to pick a new delivery slot.
  6. Contextual Handoff: If the customer asks to speak with someone, the agent can transition the SMS thread into a live voice call within the same interface, maintaining the transcript.

Step-by-Step: How to Enable This Feature

To set up expanded SMS using Azure Communication Services (ACS), follow these steps:

  • Step 1: Provision ACS Resource

Log into the Azure Portal and create an Azure Communication Services resource.

  • Step 2: Connect to Dynamics 365

In the Contact Center admin center, go to Channels > SMS. Select Add Channel and choose Azure Communication Services.

  • Step 3: Get an SMS Number

Follow the prompts within the ACS interface to purchase or port a toll-free or long-code phone number capable of SMS/MMS.

  • Step 4: Configure Workstream

Create a new Workstream for the SMS channel. Define the routing rules (e.g., route all SMS with the keyword “Order” to the Shipping Queue).

  • Step 5: Enable Two-Way Messaging

In the SMS channel settings, ensure the “Enable two-way SMS” toggle is set to On. This allows agents to reply to incoming messages rather than just sending outbound alerts.

  • Step 6: Set Up SMS Templates

Navigate to Workforce Management > Templates and create standardized SMS replies to ensure consistent branding and speed of response.

Infographic: SMS Channel Comparison

FeatureBasic SMS (Legacy)Expanded SMS (New)
Communication FlowOne-way (Notifications only).Two-way (Full conversation).
Media SupportText only.MMS (Images, PDFs, Links).
Routing LogicStatic/None.Unified Routing (Intent-based).
PlatformThird-party gateways.Native Azure Communication Services.
ContextIsolated messages.Full CRM Context & Timeline.

References

AI Foundry, contact-centre, copilot-studio, Customer-service, Power Apps

Empowering frontier firms with the Case Management Agent in Dynamics 365 Contact Centre

Empowering frontier firms with the Case Management Agent (Advancing autonomous and semi-autonomous case lifecycle management in Dynamics 365 Customer Service).

Real-time User Journey

This journey illustrates the Fully Autonomous workflow for an email-based customer inquiry:

  1. Inquiry Receipt: A customer sends an email regarding a malfunctioning device.
  2. Autonomous Creation: The Case Management Agent (CMA) detects the intent, creates a new case, and automatically populates fields (Priority, Product Category, etc.) using AI-powered prediction.
  3. Intelligent Triage: The CMA realizes it needs more details. It automatically sends a follow-up email to the customer with specific clarifying questions.
  4. Resolution Logic: Once the customer replies, the CMA searches the knowledge base and triggers a custom agent (configured with the firm’s specific troubleshooting logic).
  5. Proposal & Follow-up: The CMA drafts and sends a resolution email. It then waits for a predefined interval (SLA-based).
  6. Autonomous Closure: After sending a satisfaction confirmation and receiving no further objections within the set timeframe, the CMA closes the case and triggers the Knowledge Management Agent to document the fix.

Step-by-Step: How to Enable This Feature

To enable and configure the Case Management Agent, follow these administrative steps:

  • Step 1: Admin Center Access

Sign in to the Customer Service admin center or Contact Center admin center.

  • Step 2: Navigate to Autonomous Agents

Go to Operations > Insights > Autonomous service agents (preview).

  • Step 3: Configure Case Creation Rules

Under the CMA settings, define the field mappings and business context (e.g., which channels like email or chat should trigger the agent).

  • Step 4: Set Resolution Parameters

Select the Knowledge Bases the agent should access and link any Custom Agents or Power Automate flows required for specialized resolution logic.

  • Step 5: Define Communication Templates

Choose the email templates for “Clarifying Questions” and “Proposed Resolution.” Set the Timing Intervals for follow-ups and the conditions for automatic closure.

  • Step 6: Toggle Autonomy Level

Decide if the agent should run in Semi-autonomous mode (drafting for human review) or Fully autonomous mode (direct interaction with customers).

Infographic: CMA Lifecycle Automation

PhaseCapabilityBenefit
CreationAuto-detection of intent across voice, chat, and email.Eliminates manual data entry and triage.
ResolutionDrafts context-aware emails; triggers custom logic.Accelerates time-to-resolution with expert accuracy.
EscalationProactively identifies when a human or supervisor is needed.Ensures complex issues never fall through the cracks.
Follow-upSLA-based check-ins to ensure customer satisfaction.Improves customer sentiment without agent effort.
ClosureFully automated case resolution and record update.Maintains clean data and closes the “Knowledge Loop.”

References