Customer-service, contact-centre

2026 World Leaders in Contact Center WFM – Competitive Landscape and a Comparison against Microsoft Dynamics 365 WFM

The year 2026 is one where the contact center market sees a dramatic disruption of the long-standing Workforce Management (WFM) paradigm, which has historically been grounded in a rigid and mathematical interpretation of Erlang C and Excel-driven scheduling. Today, the industry is dominated by a new wave: Agentic AI, Predictive Intraday Automation and a move from “Resource Optimization” to “Workforce Engagement Management” (WEM).

As organizations shed the skin of legacy on-prem WFM, a new hierarchy of world leaders has emerged: titans such as NICE, the newly merged Verint-Calabrio behemoth and Genesys have been dominant for years. But the emergence of Microsoft Dynamics 365 Workforce Management (WFM) and its 2026 Wave 1 ‘Agentic’ updates present a new disruption for enterprises already integrated within the Microsoft ecosystem.

1. The 2026 World Leaders: An Overview

The WFM marketplace today is bifurcated into “Best-of-Breed” specialist solutions and “CCaaS-Integrated” platforms.

  • NICE (CXone & IEX)

NICE remains the market share leader within the enterprise market for WFM solutions. IEX WFM is the current “gold standard” for complex, multi-site contact center environments. In 2026, NICE has placed heavy emphasis on its Cognitive Load Optimization feature; this doesn’t only consider agent availability, but the “mental toll” that an agent may have sustained during a previous customer interaction based on the interaction’s complexity.

  • Verint + Calabrio (The 2025 Merger)

The acquisition of Calabrio by Verint in 2025 and orchestrated by private equity firm Thoma Bravo, has formed a “Two-Pronged” titan within the WFM space. Verint WFM supports high-end enterprise needs and is known for its deep, hierarchical permission structure. Calabrio ONE, conversely, has maintained its footing as a nimble, AI-first solution specifically geared towards the mid-market. The merged roadmap for 2026 features TimeFlex Bot, an industry-first mechanism that allows agents to trade shifts on a voluntary basis via a “FlexCoin” economy.

  • Genesys Cloud CX

The entire base of Genesys’ CCaaS platform is now fully migrated to the cloud, where their WFM capabilities are also managed. The WFM offering at Genesys is underpinned by the “Automatic Best Method” forecasting engine. This feature employs machine learning to simultaneously test a myriad of forecasting algorithms against historical data in an effort to find the optimal predictive model. Genesys also leads the market in 2026 with its “Conversational Administration”; supervisor may adjust workforce management through a natural language Copilot.

2. Microsoft Dynamics 365 WFM: The New Contender

Microsoft’s move into the WFM space started out as a “native” addition to their Dynamics 365 Customer Service solution. Now, by May 2026, it has grown to become a robust, standalone application within the broader Dynamics 365 Contact Center Suite. Unlike legacy WFM players who “layered AI on top” of existing databases, Microsoft has built their WFM around an autonomous “Scheduling Operations Agent“. This agent actively monitors real-time traffic patterns, providing immediate and proactive suggested, or even automated adjustments to the contact center schedule.

Microsoft D365 WFM Key Differentiators (2026):

  • Native Copilot Integration: Microsoft D365 WFM is itself effectively a specialized GPT-based agent, integrated into either the Microsoft Teams client or the Dynamics 365 dashboard, thereby placing these insights within easy view of supervisors.
  • Power Platform Extensibility: Organizations are given the capability to develop and customize WFM actions through the creation of Power Automate flows. As an example, if an organization’s CSAT metrics dip below 3.0, an automated coaching break for the associated team members can be triggered through such a flow.
  • Unified Data Schema: Given that WFM, CRM, and CCaaS components all share Microsoft Dataverse, information passes with zero latency. A customer interaction is completed, and the agent’s time reporting will update to reflect the agent’s true vs. Scheduled activity time, in real-time.

3. Feature-by-Feature Comparison: 2026 Edition

Feature CategoryNICE IEX / CXoneVerint / CalabrioGenesys CloudMicrosoft Dynamics 365 WFM
Forecasting Engine45+ AI algorithms; “Best Pick” logic.Predictive Actions with “Why” explanation.ML-based “Automatic Best Method.”AI-driven “Scheduling Operations Agent.”
Agent EmpowermentMobile app with deep shift-bidding.TimeFlex Bot & FlexCoin economy.Gamified performance dashboards.Teams-native self-service & Copilot prompts.
Intraday MgmtCognitive load balancing.Predictive intraday coaching.Real-time “Anomaly Detection.”Autonomous schedule re-optimization.
IntegrationStrong but often requires API work.Open platform; “Bot-first” strategy.Deeply native to Genesys CCaaS.Native to Dataverse/M365.
Complexity LevelHigh (Requires dedicated analysts).Moderate (Balanced for mid-market).Low-Moderate (User-friendly).Low (Designed for “Citizen Admins”).

4. Going Deep: Forecasting & AI Maturity

The “Black Box” vs. “Explainable AI”

One of the biggest battles to be fought in 2026 is Explainable AI (XAI).

  • NICE is still the king of the “Black Box”; its algorithms are tremendously accurate, but extremely hard for a human planner to reverse-engineer.
  • Microsoft and Calabrio have leaned into Predictive Actions, and in Microsoft’s case, its Scheduling Agent offers a “Reasoning Sidebar” that explains why it made a change (“Suggested change due to 14% spike in ‘Return Policy’ queries in the UK region”).

Microsoft’s Edge: The Dataverse Advantage

The greatest detriment to a NICE or Verint solution is the “Integration Tax”. Systems pull from the ACD or CRM using APIs, which results in data silos. Microsoft Dynamics 365 WFM works within the Dataverse and because it sees the data real-time, it is able to provide forecasts that take into account business events, such as a marketing email blast or a product recall, before they even hit the contact center queues.

5. Scheduling & the “Gig-ification” of the contact centre

The agents in 2026 continue to have very flexible schedules. All of the global leaders are incorporating a “Gig-style” scheduling approach to their tools.

Verint’s FlexCoins

The TimeFlex Bot for Verint is a standout feature here. Agents receive “FlexCoins” for picking up unwanted shifts or spikes in volume. They are then able to “spend” the coins to take off a Friday afternoon, without the need for manager approval. For Verint-powered centers, this has translated into an average reduction of 22% agent churn.

Microsoft’s Teams-Native Approach

Microsoft takes an invisible WFM approach. Its agents are managing their schedules through Microsoft Teams rather than a separate login and portal.

 Agents manage shift swapping via a Copilot chat.

 Instead of supervisors finding time in the day for training, the Scheduling Operations Agent finds lulls and notifies agents that their training module on ‘New Product’ is ready with a Teams message: “Hi, volume is low. Ready for your ‘New Product’ training module?”.

6. Strategic analysis: which platform is for you?

The enterprise power user: NICE IEX

If your contact centre supports 5,000+ agents across 10 countries with complex union labor laws, then NICE remains the superior platform. Its ability to simulate and work with “Union Constraints” and “Multi-Skill Simulation” is far more advanced than what Microsoft offers at present.

The innovation seeker: Verint/Calabrio

For organizations where “Employee Experience” (EX) is key, the merger between Verint/Calabrio delivers the most innovative tools. Currently, its TimeFlex Bot is the only solution to effectively incorporate the gamification of scheduling to this extent.

The All-Microsoft Shop: Dynamics 365 WFM

For a medium-large sized enterprise that already utilizes Microsoft Dynamics 365 Sales and Microsoft Teams, the justification for a 3rd-party WFM solution begins to diminish. Microsoft has significantly closed the “Functionality Gap” in 2026 for the typical contact centre, making it suitable for 90% of use cases. The Total Cost of Ownership (TCO) is drastically reduced due to the elimination of integration costs, data storage, and more.

7. Best-of-Suite vs Best-of-Breed Analysis

The classic best-of-breed vs. Best-of-suite debate comes to a head in 2026. Where the early 2010s championed the “best-of-breed” philosophy, we are now firmly entrenched in the era of The Great Consolidation.

Best-of-Suite (The “Platform” Approach)

With this approach, you select a primary vendor, such as Microsoft, Salesforce, or Oracle, to provide a range of integrated tools from CRM to WFM to Communication to Analytics all operating under a single data schema.

The Philosophy: Seamlessness over specialization.

 The 2026 Edge: Agentic AI. With all of your data in a single “Dataverse,” AI agents have the entire picture of the customer journey without complex API calls.

Best-of-Breed (The “Specialist” Approach)

Here, you select the best tool for each specific task, such as NICE for WFM, Zendesk for Support, or Slack for Communication and then build out complex integrations.

 The Philosophy: Performance over integration.

 The 2026 Edge: Deep innovation. Specialists generally lead the market in the release of unique, impactful features (like NICE’s Cognitive Load tracking) by an average of 12-18 months over the suite players.

The Core Comparison

FactorBest-of-Suite (e.g., Dynamics 365)Best-of-Breed (e.g., NICE / Calabrio)
IntegrationNatively Unified. Data flows instantly between modules (WFM → CRM).The “Integration Tax.” Requires APIs, middleware, and maintenance.
User ExperienceConsistent. One UI, one login, one training curve.Fragmented. Different “looks and feels” for every tool.
Feature Depth80/20 Rule. Covers 80% of needs; might lack niche “edge cases.”Deep Excellence. Highly granular controls for power users.
AI StrategyCross-Functional. Copilot sees everything across the business.Domain-Specific. AI is incredibly smart but only within its own silo.
Vendor Management“One Throat to Choke.” Simplified billing and support.Multiple Partners. Complex licensing and potential “finger-pointing.”

Why the change

It is not just about cutting costs-it’s about Data Velocity. “Batched” data in 2026 is too slow to keep up. When your 15-minute CRM sync with your Best-of-Breed WFM takes over your intraday AI schedule, you’ve already failed. With a suite approach, you get Zero-Latency Orchestration. > The “Integration Tax” warning. Studies suggest every $1 spent on a Best-of-Breed Subscription adds $0.40-$0.70 to integration, maintenance and data cleansing costs to keep the entire stack functioning correctly.

The “Decision Matrix”

Choose Best-of-Suite IF:

  • You are heavily invested in one particular ecosystem (Microsoft Dynamics/365, etc.).
  • You care most about Total Cost of Ownership (TCO) and minimizing IT overhead.
  • Unified AI (Copilot) is your priority across multiple business units.
  • You have a Citizen Developer mentality.

Choose Best-of-Breed IF:

  • There is a specific function you must perform (i.e., Union law complexity for WFM) that requires specialized capability.
  • A particular function (i.e. WFM) is a “Core Competency” rather than a support function.
  • You have a massive IT / DevOps team that can manage a “Composable” stack.
  • There’s a capability that has not yet been built by the major suites.

8. Summary

The market has evolved from recording what happened, to forecasting what will happen, and finally to executing on behalf of the user.

  • NICE and Genesys are leading the pack with accuracy and scale.
  • Verint is leading with agent autonomy.
  • Microsoft is leading with integration and ecosystem coherence.

In 2027, we’re going to see the role of the “Workforce Manager” become the “Bot Orchestrator.” The winning platform isn’t going to be about just having the best math; it’s going to be about providing an experience agents are excited about and enabling supervisors to be on autopilot.

Key Takeaway: Stick with the existing leaders if deep technical functionality and global compliance are critical to your business; otherwise, look to Dynamics 365 WFM as a leading, fast-paced, AI-driven choice for all other operational needs within the Microsoft ecosystem.

We’re noticing a trend towards “Hybrid-Suites,” where businesses opt for a Core Suite solution and then “bolt-on” a Best-of-Breed capability for a highly specific function where they need world-class performance.

9. Appendix (Contact Centre & CCaaS KPIs)

These are critical KPIs for Contact Centres and CCaaS environments in 2026, structured by five key pillars for strategic insight:

  • Operational Efficiency
  • Customer Experience (CX)
  • Agent Experience and Workforce Management (WFM)
  • AI and Self-Service Performance
  • Financial Performance

In 2026, we see a shift in KPI usage from “Historical Reporting” to “Predictive Orchestration,” where the aim is not only to understand what happened, but to proactively shape future outcomes.

Pillar 1: Operational Efficiency KPIs

These are the “Engine Room” metrics that enable smooth contact center operation.

1. Average Handle Time (AHT)

This metric continues to be the standard of contact center efficiency, quantifying the complete duration of a customer interaction from start to finish, including post-call work (ACW). In 2026, the objective shifts from solely reducing the length of calls to analyzing the agent’s workflow for “friction points.” High AHT can point to either inadequate tools or lack of real-time AI assistance, while an ideal AHT signifies that agents possess the necessary information to resolve customer issues swiftly.

2. First Contact Resolution (FCR)

Arguably the most crucial operational metric, FCR measures the proportion of customer queries resolved during their initial contact. High FCR is highly desirable as it reduces operational expenses and boosts customer satisfaction. For CCaaS platforms, FCR increasingly extends to cross-channel interactions, ensuring that a customer journey initiated by a bot and then escalated to an agent is still classified as a “first contact” if resolved during that session.

3. Service Level (SL)

Service Level defines the proportion of customer interactions handled within a set time frame, typically expressed as “X% of calls answered in Y seconds.” This metric is a direct indicator of both staffing adequacy and the precision of workforce management practices. 2026 is seeing an increase in dynamic SLs, where AI-driven platforms automatically adjust targets in real-time based on fluctuations in demand and the customer’s priority, ensuring that high-value customers receive preferential handling.

4. Occupancy Rate

Occupancy Rate gauges the proportion of an agent’s scheduled work time spent actively engaging with customers (talking time, hold time, and ACW). While a high occupancy rate can seem to indicate peak efficiency, persistently high levels can contribute to agent burnout. Advanced WFM solutions like NICE IEX and Microsoft Dynamics 365 are incorporating “automated micro-break” triggers to provide agents with necessary breathing space between demanding interactions.

5. Average Speed of Answer (ASA)

ASA measures the average time a customer spends in the queue before reaching an agent. This metric significantly impacts the initial customer experience. While CCaaS platforms now offer “callback” features to alleviate wait times, ASA remains a key health indicator for the contact center. In 2026, ASA is often analysed based on customer intent to ensure that urgent inquiries are addressed more quickly than general ones.

6. Abandonment Rate

The percentage of customers who hang up before connecting with an agent or completing a self-service interaction is the Abandonment Rate. A high rate is a “red flag” for both potential lost revenue and diminished brand image. Across omnichannel CCaaS platforms, abandonment tracking is expanding to digital channels, identifying points where customers abandon a chat or messaging session due to slow responses or confusing chatbot navigation.

7. Call Volume & Channel Mix

This metric focuses on the total number of incoming interactions, and the proportion each channel takes. This is vital for 2026 workforce planning, since it helps define where customers are going, and where the center might be over-investing. If 70% of calls are happening on WhatsApp but 70% of agents are dedicated to Voice, “Mismatched Channel Mix” becomes a primary failure point.

8. After-Call Work (ACW) Time

This KPI defines the time the agent spends updating CRM notes, sending follow-up emails, or closing out after the customer has hung up. Agentic AI and ‘Auto-Summarization’ have reduced ACW times considerably in 2026 – Microsoft Dynamics 365 WFM’s Copilot, for instance, produces a real-time summary of the call allowing the agent to move onto the next interaction in seconds rather than minutes, boosting “Active Capacity”.

9. Longest Delay in Queue (LDQ)

This KPI differs from ASA by focusing on “worst-case scenario” for a customer. The LDQ is the time the single longest waiting caller waited to speak with an agent, and is critical in uncovering the “edge cases” when a specific queue (i.e. Spanish-speaking customers, high-priority technical issues) are critically understaffed and have customers slipping through the cracks.

10. Transfer Rate

Transfer rate is the proportion of interactions that an agent passes off to another agent or supervisor to get an answer. This is indicative of weak “Skills-Based Routing” or an overall problem with training. An intelligent CCaaS setup will pre-qualify customers with enough accuracy using AI that the transfer rate will drop to zero, as customers get seamlessly matched to an agent that can address their need directly.

Pillar 2: Customer Experience (CX) & Quality KPIs

Metrics that focus on the emotional and functional success of the interaction; these are “Heart” metrics.

11. Customer Satisfaction Score (CSAT)

Often acquired by a post-interaction survey asking, “How satisfied were you with the service you received today?” While it’s a standard metric, in 2026, contact centers use AI sentiment analysis on each and every call to obtain “Continuous CSAT”. This gives an organization a more accurate view of the brand’s overall health.

12. Net Promoter Score (NPS)

This metric identifies the long-term health and loyalty of an organization’s brand. Customers are asked how likely they are to recommend a brand to others on a 0-10 scale. While it’s different than CSAT in that it doesn’t look at individual transactions, it serves as an indicator of “Relationship”, and is influenced by the quality of an organization’s “Service Recovery”.

13. Customer Effort Score (CES)

This KPI measures how much effort the customer expended to get their issue resolved. In 2026, CES is a better predictor of churn than CSAT, and reflects the fact that customer defection can often be linked to “high-effort experiences” like being bounced between agents, or forced to navigate an unnecessarily complicated IVR. CCaaS now takes a holistic look at customer journey and identifies points of potential high effort, then designs them out.

14. Sentiment Score (AI-Driven)

Using natural language processing, this KPI assigns a “positive, neutral, or negative” score to the customer’s interaction, based on tone, cadence, and word choice. The contact center can utilize these scores to address “angry” callers proactively (via supervisor whispers) or even to identify agents that have effectively turned a negative interaction into a positive one.

15. Quality Assurance (QA) Score

Historically a manager listening to just 2-3 calls per agent per month, this has evolved into “Automated QA” which reviews 100% of interactions against compliance (adhering to the script and legal guidelines) and empathy standards, ensuring that all interactions maintain “Human Quality”.

16. Customer Churn Rate (Attributed to Service)

This KPI specifically targets customers who leave an organization following a negative contact center interaction. The combination of CRM data with call logs now allows organizations to see the precise “Cost of a Bad Call”, and this is being used to justify the investment in WFM and AI.

17. Resolution Time (End-to-End)

Instead of AHT, resolution time takes into account the total clock time from an issue being opened until it’s completely resolved (including any “Pending” or “Escalated” time). While complex technical support might yield a 5-min AHT and 3-day resolution, and so on. This KPI must be reduced for B2B environments (where Downtime means money out the door).

18. Interaction Consistency

One KPI to keep track of how consistent a customer’s experience is across channels. If I have an extremely “Friendly and Fast” experience on Twitter, and a “Rude and Slow” experience on the phone, then the brand has interaction inconsistency. The “Unified desktop” environments of CCaaS platforms will ensure agents have the same context and tone-of-voice rules irrespective of the customer’s channel of contact.

19. “Voice of the Customer” (VoC) Insights

VoC is not really a single number, but a categorized KPI (and essentially the ‘Top 5 Reasons for Calling’). In 2026, the same will be automatically gathered via an AI theme extraction. The moment “Difficulty Logging In” hits the #1 spot on this graph, then the contact center becomes the ‘early-warning’ to the product team that something must be done immediately (to address it).

20. Hold Time & Silence Ratio

High “Silence Ratios” (where neither agent nor customer is talking) will signal a “Slow System” or an agent who doesn’t know how to answer, forcing them to look for the correct info/answer, thus being monitored by IT and WFM for “System Latency” or training issues. The desire here would be to replace silence with “Proactive Engagement” or, in its absence, have minimal silence using integrated knowledge management.

Pillar 3: Agent Experience & Workforce Management (WFM) KPIs

The “engine” metrics focused on employee well-being and productivity:

21. Agent Attrition Rate

The percentage of the workforce leaving over a certain time period, contact centers are historically well known for high turnover (typically 30-45%) and in 2026 reducing attrition is still a top priority. High attrition leads to a “Brain Drain” and enormous recruitment costs. Here “Predictive Attrition” has emerged and WFM will identify certain agents whose performance or mood are dipping and allow for “Stay Interviews.”

22. Schedule Adherence

This tracks how accurately agents stick to their scheduled tasks. If you’re supposed to be “on phones” at 9 am but only clock in at 9:05 am your adherence drops. Once considered a “Big Brother” metric, today WFM shows agents the information about their adherence in real time for transparency purposes, showing them how their presence affects the workload on the team.

23. Employee Satisfaction (ESAT) / eNPS

This is the “internal CSAT” metric that tells the leadership if employees are happy with their jobs (based on tools, management and balance). With a “War for Talent” underway ESAT has become a board-level metric. High ESAT will correlate with high CSAT (happy employees mean happy customers) and systems like Microsoft (through Teams/Dynamics) integrate ESAT surveys on-the-fly for “pulse” checks on how agents are feeling.

24. Shrinkage

This is time agents are paid for but are not available for customers (vacation, sick leave, training, coaching and even toilet breaks). Measuring accurately is critical for “Capacity Planning” and if a manager fails to properly account for a 25% shrinkage, they will consistently be short on staff and see both their ASA and agent burnout numbers skyrocket.

25. Absenteeism Rate

While “shrinkage” implies Planned absences, absenteeism is an Unplanned absence, it’s a “canary in the mine” for the environment. In 2026, “trend analysis” of absenteeism will tell managers that when absenteeism jumps on Fridays, or after certain stressful periods, they need to address the cause rather than punish the symptom.

26. Coaching & Training Hours

This metric reflects how much time is being spent on employee development. Coaching is often the first sacrifice made when call volumes rise, yet in 2026 the investment in agent development is considered a “Critical Success Factor”. WFM systems now “protect” coaching time, ensuring that even at the busiest of times, employees get that needed 30-60 min block of time where they will be developed.

27. Internal Promotion Rate

This metric represents how many of leadership or specialized roles are filled by former front-line employees. A high internal promotion rate will serve as a powerful recruitment and retention tool in 2026 and signals a strong “Career pathing” program, convincing agents this is not a “dead end” but a career opportunity.

28. Occupancy Variance

While Average Occupancy tells you how busy an agent was, it doesn’t show how much that work is balanced across the team. If one agent has 95% occupancy and another has 60% it means one is getting “slammed” with work while the other has nothing to do due to the lack of “Skill-Based Routing.” Reducing Occupancy Variance is essential for agent equity.

29. “Speed to Competency”

This KPI indicates how quickly a new agent achieves the “Baseline Performance” (i.e. AHT, FCR) of an established agent. In 2026, “AI-driven on-the-job training” has drastically reduced this metric, with the AI suggesting “Next best action” for the agents, and “Newbies” working like “Veterans” within days, not weeks.

30. Agent Autonomy Score

This modern KPI measures how much control the agent has over their life (self-scheduling, swapping shifts, selecting channels). High agent autonomy has become the #1 factor for agent retention in 2026, measured by the usage of “self-service WFM” and agent input.

Pillar 4: AI, Automation & Self-Service KPIs

The “future” metrics that measure the effectiveness of non-human interactions:

31. Self-Service Containment Rate

This KPI shows how many customers start a journey in a self-service channel and complete it without talking to an agent. However, you need to be careful about “Containment Rate” – just because an interaction is contained doesn’t mean it’s successful, or that the customer isn’t frustrated. Therefore, the key is “Containment Rate & CSAT.”

32. Bot-to-Human Handover Rate

This metric measures how often a bot ‘fails’ and hands over the call/chat to an agent. A high rate means the bot’s “Intent Recognition” isn’t strong enough or that it hasn’t been trained on the right things. The 2026 goal is “Warm Handovers,” where 100% of context is transferred.

33. AI Intent Recognition Accuracy

This KPI measures how accurate the NLU is in identifying the customers ‘reason for calling’. If a customer has “My bill is too high”, is it categorized as a “Billing Inquiry” or a “Churn Risk”? Improving this metric is foundational to better routing and automated self-service.

34. Zero-Touch Resolution (ZTR)

ZTR is the holy grail of AI ops. It looks at how many interactions the AI completed soup-to-nuts, including actually performing backend API functions such as making the refund or changing the address. Unlike simple ‘Deflection,’ it indicates real work being done by machines and allows the human resources to focus on ‘High-Empathy’ cases.

35. Knowledge Base (KB) Effectiveness

This KPI shows how many interactions actually result from using a knowledge base article. In 2026, CCaaS platforms provide ‘Page Value’ metrics-if a user views a help article and then immediately calls into the contact center anyway, it receives a ‘Low Effectiveness Score’ and will be rewritten or reworded by the content team.

36. AI ‘Hallucination’ Rate

The holy grail in Generative AI (LLM) worlds where a critical element is measuring the occurrences of incorrectly generated or ‘made-up’ information. This metric is typically assessed with a ‘Human in the Loop’ system that provides auditing data where a QA agent flags when an AI either unauthorizedly grants a discount or provide incorrect technical instructions. The goal is to keep this at ~0% for brand and legal safety.

37. Deflection Rate (Proactive)

Proactive Deflection shows the number of interactions avoided simply by proactively contacting the customer before the problem actually occurs. For instance, detecting a shipment delay and sending a proactive automated text notification ensures the customer does not call to ask, ‘Where’s my shipment?’. This is the quintessential ‘Efficiency’ KPI-it actually reduces the work performed within the contact center.

38. IVR Abandonment by Node

This detailed KPI identifies exactly which prompt in the “Press 1 for Sales” menu that callers actually hang up. If 40% hang up at “Node 3,” it signifies that prompt is likely too confusing or too long. In 2026, ‘Visual IVRs’ and ‘Conversational IVRs’ are replacing the node system, but the ‘Path Abandonment’ metric is the equivalent.

39. Copilot Usage/Adoption Rate

For businesses utilizing the Microsoft Dynamics 365 suite or a similar integration, this measures the percentage of interactions where the agent actually utilizes an AI suggestion. If agents are not selecting the “Suggested Responses” they may be doing so because the AI’s assistance is not valuable or the agents have not been trained on how to effectively “Co-pilot” their interactions.

40. Sentiment ‘Flip’ Rate

This AI-powered metric analyses how many interactions started with ‘Negative Sentiment’ and finish with ‘Positive Sentiment’. This is a sophisticated de-escalation metric that identifies the “Empathy Heroes” of your workforce.

Pillar 5: Financial & Strategic Growth KPIs

The “Bottom Line” metrics that tell the CFO how the contact center drives value.

41. Cost Per Contact (CPC)

The total operating cost of the contact center-including all labour, technology, and facilities-divided by the total number of contacts handled. While lower is better, leaders in 2026 understand that “Cheap isn’t always Better.” An interaction handled for $2.00 that doesn’t resolve the customer issue, costs far more than a $10.00 human interaction that results in a $1,000 renewal.

42. Customer Lifetime Value (CLV) Impact

Modern CCaaS platforms can now track changes in CLV from individual contact center interactions. When customer “Spend” increases by 20% as a direct result of a high-quality interaction, the contact center has proven “Value Add” rather than a mere “Cost Center.”

43. Revenue per Successful Interaction

For centers handling sales or “Up-selling”, this KPI calculates the average dollar value received for each completed interaction. Support centers are also now evaluated on this, as AI “Next Best Actions “prompt agents to “Up-sell” customers on complementary products or services during an interaction.

44. ROI of Contact Centre Technology

This KPI is designed to quantify the financial return from investments in a WFM suite, AI bots, or moving to a cloud environment. The “Payback Period” metric calculated by ROI identifies how many months of labour savings or increased FCR it takes for the new technology to offset its upfront cost. Most modern CCaaS transformations achieve “Payback” between 12-18 months.

45. Cost of Inaction (COI)

This strategic metric, typically used by consultants, demonstrates what the organization loses by not investing in updated technology (e.g., lost revenue due to high abandonment, wasted labor due to redundant systems, compliance fines). It serves as the key “Business Case” for moving from legacy systems to modern platforms such as Microsoft Dynamics 365.

46. Agent Utilization (Financial)

Unlike ‘Occupancy,’ financial utilization measures the amount of “Revenue-Generating” or “Value-Protecting” time each agent dedicates to an interaction relative to their overall labour cost. This demonstrates the “Gross Margin” for each human agent and guides decision-making about outsourcing low-value tasks.

47. Customer Acquisition Cost (CAC) via Referrals

By tracing NPS and “Recommendation” data to the contact center, the business will be able to determine the number of new customers who were gained because they experienced a “Wow” moment during their interaction. This KPI will significantly bolster the contact centre’s reputation as a “Referral Engine.”

48. Compliance Penalty Avoidance

For “Regulated Industries,” the most crucial contact center metric could be “Zero Fines.” This metric helps the organization identify how many interactions were successfully “Audit-Proofed” using AI compliance tools, effectively avoiding large penalties that can result from mis-selling or data breaches.

49. Tech Stack Consolidation Savings

This metric quantifies how much a business saves by migrating from a “Best-of-Breed” to a “Best-of-Suite” technology approach. Typically, by migrating from 10 separate licenses to a single Microsoft or Salesforce product, a business will save 15-25% in “SaaS Overlap.”

50. Carbon Footprint per Interaction

As ESG (Environmental, Social, and Governance) goals become a corporate imperative, the “Green Cost” of each interaction is becoming a critical metric. This metric measures the total energy consumption for both data centers (cloud vs. On-prem) and the reduction in carbon emissions due to 100% of the workforce operating remotely.

The shift from 2025 to 2026 demonstrated that KPIs are no longer simply used to count things; they are intended to measure people. Whether leveraging a standalone “Best-of-Breed” WFM tool or the integrated Microsoft Dynamics 365 suite, the goal should remain the same: achieve a “Balanced Scorecard” where Efficiency, Empathy and Economics are all equally measured.

Uncategorized

Microsoft Build 2026 Summary

Microsoft Build 2026, held from June 2nd to June 3rd both online and in San Francisco, marked a monumental shift in the technology landscape. For the past several years, the developer ecosystem has been relentlessly focused on the foundational capabilities of large language models, the integration of conversational copilots, and the iterative improvements in generative AI outputs. However, the narrative emerging from this year’s developer conference has fundamentally altered that trajectory. Microsoft has officially declared the end of the passive chatbot era and the dawn of the agentic operating model. This paradigm shift involves intelligent agents performing tangible, proactive work across codebases, data repositories, cloud infrastructure, and operational security boundaries.

The tech world has seen several paradigm shifts, and the move toward pervasive, agentic AI is arguably the biggest yet. Microsoft’s 2026 Build conference laid this clearly on the table for developers: it’s not just about playing with AI and standalone chatbots anymore. It’s about building, managing, and governing long-running agentic systems that can reliably execute complex, real-world workflows at scale. Build 2026 presented a detailed roadmap for the future of business software. Below is a breakdown of the most important announcements, strategy shifts, and technological advancements that marked the 2026 Microsoft Build.

1. The Enterprise AI Shift: Emancipation and the Pursuit of Superintelligence

The most impactful announcement at Build 2026 wasn’t a product but a strategic confession from Microsoft’s AI chief, Mustafa Suleyman. While the public narrative has often painted Microsoft as being in direct competition with consumer-focused tech giants Suleyman revealed that his “superintelligence” team is primarily focused on AI research. “We were only sort of set free from our contract with OpenAI about six months ago to formally pursue superintelligence,” Suleyman stated. He emphasized that while these are very early days for the initiative, the mandate is clear.

The Wake-up Call of “Cowork”:

The year saw Anthropic release “Cowork,” an AI that allows users to automate tasks and generate code without having prior programming experience. Its release caused a substantial sell-off in Microsoft shares, plummeting 10% due to fears that Anthropic’s new tool would disrupt established enterprise software platforms.

According to Suleyman, Anthropic’s direct challenge to the corporate world with its advanced development tools poses a far greater threat to Microsoft’s core business than consumer chatbots do. “We’re more focused on the Anthropic-style which is enterprise [use cases], developers and coding. That’s the journey we’ve been on,” he stated.

The Drive Toward Autonomy:

Microsoft is now accelerating its quest for true self-sufficiency. While maintaining a reformed, $30 billion cloud partnership with OpenAI (holding a 27% stake and guaranteed access until 2032), the company is investing heavily in its own internal AI models. This hybrid approach (partnering with OpenAI while concurrently investing $5 billion in Anthropic and building its own tech under Suleyman) highlights Microsoft’s determination to lead in the “thinking and coding” agent domain, an area focused on developing intelligent agents that can autonomously execute complex, multi-step business processes.

2. Intelligence Embedded in Context: Introducing Microsoft Agent Platform and Microsoft IQ

The race to move AI from experimental to operational has hit a wall: context. Raw model performance is no longer the bottleneck, but rather how an agent comprehends the specifics of a business, accesses trustworthy internal knowledge, and adheres to appropriate governance constraints.

To tackle this, Microsoft unveiled Microsoft IQ, an enterprise intelligence layer that provides Copilots and agentic systems with a shared, evolving understanding of how an organization functions. Microsoft IQ integrates data from across an entire customer’s Microsoft environment and is divided into four categories:

Work IQ

Slated for general release on June 16, 2026, Work IQ injects workplace intelligence into agents by building semantic understanding of emails, calendars, meetings, chats, documents and internal business applications. Its set of APIs (covering Chat, Context, Tools, and Workspaces) allow for production-ready interaction between agents and M365 data, within the strict boundaries of M365 tenant trust, ensuring all actions are auditable and discoverable.

Fabric IQ

Generally available today, Fabric IQ maps the data operations of a business. It imbues semantic meaning into relationships between entities like customers, orders, revenue and products, and ensures consistency regardless of where that data lives, be it in ERP or CRM systems.

Foundry IQ

Foundry IQ allows agents to discover and reuse knowledge found in a diverse range of enterprise data sources, custom applications and internal web pages.

Web IQ

The new standard for AI grounding, Web IQ combines proprietary enterprise data with real-time information from the internet, enabling enterprise agents to reconcile internal knowledge with current world events.

By consolidating these data points, the Microsoft Agent Platform enables developers to build governed, enterprise-ready bots on GitHub and deploy them through Microsoft Foundry with automatic optimization.

3. The New MAI Family: Homegrown AI Models for Choice

To empower this new paradigm of agentic software, Microsoft introduced its new set of seven internal AI models, branded under the “MAI” (Microsoft AI) umbrella, designed to give developers unparalleled choice across the entire tech stack.

Advanced Reasoning and Coding:

In direct response to Anthropic’s Opus 4.6, Microsoft revealed an advanced reasoning model that rivals enterprise-level coding capabilities. Additionally, an ultra-efficient model for coding has been specifically fine-tuned for the GitHub developer platform to improve the speed, cost, and reliability of code generation.

Microsoft announced a comprehensive suite of seven new AI models, engineered completely in-house by the AI Superintelligence Team. Branded under the “MAI” nomenclature, these models span a wide array of specialized capabilities, including reasoning, code generation, image creation, transcription, and voice synthesis.

At the apex of this new ecosystem sits MAI-Thinking-1. This model represents Microsoft’s most ambitious proprietary release, featuring a 35-billion-active-parameter architecture explicitly engineered for long-context reasoning, executing multi-step instructions, and performing advanced code generation. Microsoft deliberately built this model from the ground up using enterprise-grade, commercially licensed data. By abstaining from the controversial practice of relying on outputs generated by other leading competitive AI models, Microsoft ensured a pristine data lineage. This strategic data sourcing methodology significantly improves operational efficiency while simultaneously reducing the computing costs associated with running massive enterprise inferences. Microsoft claims that MAI-Thinking-1 successfully matches other leading, heavier models in its weight class across key software and operational benchmarks.

Expanding the MAI Portfolio

Alongside the flagship reasoning model, Microsoft introduced a diverse array of specialized, modality-specific models:

  • MAI-Image-2.5: A next-generation visual generation model.
  • MAI-Voice-2: A high-fidelity voice synthesis engine.
  • MAI-Transcribe-1.5: An advanced audio-to-text transcription model.
  • MAI-Code-1: A specialized coding assistant model.

This multi-model approach allows enterprise customers and developers to select the exact right size, latency, and modality for their specific architectural needs, ensuring that developers do not have to rely on a massive, expensive generalist model for simple, highly specialized tasks. 

4. The agentic app backend with Microsoft Fabric and databases

AI is changing how we do things – with the proportion of workers shifting from asking questions to giving whole tasks to multi-agent systems. This need a reliable and scalable data foundation. During the Build 2026 Microsoft announced major updates to its database infrastructure and Microsoft Fabric. The developer workflow is becoming entirely centralized. The GitHub Copilot app has now officially become the primary control center for all agentic development processes. Simultaneously, Microsoft Foundry has significantly matured, transitioning from an experimental platform into a hardened, production-grade agent deployment environment.

Rayfin: Redefining the Application Backend

To bridge the gap between AI prototyping and robust enterprise deployment, Microsoft unveiled Rayfin. Rayfin is strategically targeted at creating prompt-to-production enterprise application backends. Within the Rayfin framework, foundational data models live entirely as code, and data access policies become fully programmable entities.

Crucially, all application data managed through Rayfin seamlessly lands in Microsoft’s OneLake repository, while Fabric provides the underlying enterprise scale and security architecture. This integration ensures that highly automated, GitHub-based CI/CD workflows can efficiently drive structural changes to complex backend data systems.

Azure HorizonDB and Cosmos DB: The Data Layer of the AI Era

A foundational element of AI applications is robust, scalable PostgreSQL infrastructure. To dominate this space, Microsoft introduced Azure HorizonDB. This new database architecture completely brings PostgreSQL into the modern AI application era.

Azure HorizonDB is built with extreme reliability and scale in mind. It features zone resilience as a default characteristic. The storage architecture is massively elastic, capable of scaling up to an astounding 128 TB of capacity. On the compute side, it offers scale-out capabilities reaching up to 3,072 vCores, allowing it to handle virtually any throughput demand. Furthermore, Azure HorizonDB features deeply integrated vector search functionalities, native AI model management, and seamless operational connectivity directly to Microsoft Foundry and Fabric.

Complementing HorizonDB, Microsoft also announced significant improvements to Azure Cosmos DB. These improvements are specifically tailored to enhance local development experiences and optimize the long-term memory of AI agents. The Cosmos DB updates drastically shorten developer feedback loops and actively reduce the dependency on live cloud connections during local testing. This approach improves execution repeatability across diverse developer environments and automated build agents, enabling engineers to identify and resolve data access issues far earlier in the software development lifecycle.

5. Securing the Agentic Enterprise with MDASH

As the volume of AI-generated code explodes and software delivery speeds increase exponentially, the traditional models of application security (AppSec) are rapidly becoming obsolete. Microsoft directly addressed this critical vulnerability gap with the introduction of MDASH (Microsoft Security multi-model agentic scanning harness).

The fundamental premise of MDASH is that the AI era requires AI-native security tooling. Microsoft openly acknowledged that in the immediate future, organizations must expect vastly more code to be both generated and reviewed by artificial intelligence. Concurrently, malicious threat actors are guaranteed to utilize these exact same advanced models to discover zero-day exploits and orchestrate complex attacks.

MDASH is designed to raise the bar for enterprise AppSec by deploying agentic security systems to fight back. The platform mandates and heavily invests in highly automated code reviews, rigorous programmatic policy enforcement, isolated sandboxing environments, and continuous exploitability analysis. The goal of MDASH is not to replace the human security engineer, but rather to elevate them. By automating the repetitive, lower-tier triage and discovery phases, MDASH ensures that human security professionals remain in the loop solely for making complex, nuanced risk decisions rather than wasting time on manual vulnerability hunting.

6. Accelerating Human Progress: Scientific Discovery and the Quantum Leap

While enterprise SaaS, developer tools, and operational security dominate the corporate dialogue, Microsoft utilized the final stages of Build 2026 to showcase how its compute infrastructure is actively solving fundamental challenges in global science and advanced physics.

Microsoft Discovery: Automating the Scientific Method

Microsoft announced the general availability of Microsoft Discovery, an entirely new class of enterprise-grade, agentic AI platform built natively on Azure. The explicit purpose of Microsoft Discovery is to fundamentally alter how research and development is conducted, expanding what individual scientists can achieve by applying agentic workflows across the entire scientific process.

The platform is already demonstrating massive, real-world utility across major global corporations:

  • BHP is actively deploying Microsoft Discovery to accelerate the identification of novel copper-leaching solutions, reducing research timelines from several years down to mere months.
  • Syensqo is utilizing the platform to vastly accelerate complex semiconductor research and development.
  • GSK is deploying these agentic systems to rapidly iterate on advanced pharmaceutical drug discovery processes.

To democratize this profound capability beyond the Fortune 500, Microsoft also launched a free Discovery local app tailored for the broader scientific community. Currently available in public preview, this localized application provides immense research capabilities to academic institutions and independent researchers, requiring nothing more than a standard GitHub Copilot account to access.

The Quantum Milestone: Majorana 2

In perhaps the most technically astounding hardware announcement of the conference, Microsoft unveiled Majorana 2, its next-generation quantum computing chip. While quantum computing has historically been characterized by slow, incremental progress, Majorana 2 represents a literal giant step toward true commercial scale.

The technical specifications of the chip represent a paradigm shift in physics engineering. The Majorana 2 chip achieves an astonishing average qubit lifetime of 20 seconds, with specific instances sustaining stability for up to a full minute. This architectural breakthrough provides a 1,000x increase in reliability when compared to Microsoft’s previous generation of quantum hardware. Furthermore, Microsoft has established a clear, viable engineering path to placing one million functional qubits onto a single chip that physically fits within the palm of a hand.

The integration of artificial intelligence is central to this timeline. Microsoft confidently declared that by heavily utilizing agentic AI to optimize physics models and hardware designs, the company is firmly on track to deliver a fully scalable, commercially viable quantum machine by the year 2029.

7. The Agentic Revolution: Moving Beyond the Prompt

The central thesis of Build 2026 was the transition from reactive AI to proactive, agentic AI. Microsoft unveiled two massive initiatives designed to materialize this vision: Project Solara and Microsoft Scout.

Project Solara: Rethinking Chip-to-Cloud Interactivity

Perhaps the most visually striking and forward-looking announcement was Project Solara. Positioned as a completely new chip-to-cloud platform, Project Solara is engineered exclusively for the operational needs of AI agents. Microsoft’s core objective with this platform is to radically reduce the cost and friction associated with creating AI-powered, custom-built devices across various industries and enterprise use cases.

To demonstrate the practical application of this platform, Microsoft unveiled two distinct prototype reference devices:

  1. The Project Solara Badge Device: Powered by cutting-edge Qualcomm technology, this wearable badge represents a fundamental reimagining of mobile productivity. It acts as a reference design for on-the-go, agent-first interaction, allowing a user to communicate hands-free with their AI agents while traveling or moving between corporate meetings.
  2. The Project Solara Desk Device: Leveraging MediaTek silicon, this prototype functions as an ever-present desktop companion. It acts as an always-available ambient AI assistant that maintains continuous awareness of a user’s schedule, ongoing tasks, and immediate workflow context.

Project Solara highlights Microsoft’s philosophical belief that the future of computing will not be bound to conventional screens or singular applications. Instead, computing will manifest as intelligent agents operating seamlessly and contextually across dynamically shifting physical and digital environments.

Microsoft Scout: The Autopilot for Corporate Workflows

Transitioning from hardware to pure software, Microsoft introduced Microsoft Scout, officially characterized as the company’s first “Autopilot agent for work”. Scout represents a massive departure from the standard “Copilot” model. Instead of relying on a human user to perpetually enter conversational prompts, Scout is explicitly designed to operate silently and proactively in the background, continuously managing daily tasks.

Scout is built upon the open-source OpenClaw technological foundation. It is intellectually driven by the Work IQ context engine, which allows the agent to intrinsically understand and navigate the user’s specific corporate environment. The Work IQ APIs are essential here, as they make profound layers of Microsoft 365 context natively available to these agents. This means Scout can fluidly traverse Microsoft Teams, Outlook, OneDrive, and SharePoint, while simultaneously executing local actions directly on the user’s local machine hardware.

The operational capabilities of Scout are immense. Microsoft detailed that Scout can autonomously track complex, multi-stage projects, proactively identify and resolve calendar scheduling conflicts, aggregate data to prepare comprehensive meeting briefs, and independently handle a myriad of routine workplace activities on behalf of its human counterpart.

Crucially, Microsoft has preemptively addressed the massive security implications of autonomous corporate agents. Every individual AI agent deployed through Microsoft Scout is assigned its own unique Entra identity. This profound architectural decision ensures that enterprise IT organizations can comprehensively monitor exactly what data an agent is accessing and enforce strict governance over the administrative actions it is permitted to execute. Microsoft is currently rolling out Scout on an experimental, highly controlled basis to selected Frontier organizations situated in the United States.

8. Hardware Innovations: Localizing the AI Workload

While cloud infrastructure remains Microsoft’s financial bedrock, Build 2026 clearly demonstrated that local, edge-based computational power is vital for the agentic future, leading to significant hardware unveilings.

The Surface RTX Spark Dev Box

For developers requiring immense localized power, Microsoft introduced the Surface RTX Spark Dev Box. This is a highly specialized, compact desktop workstation meticulously powered by Nvidia’s advanced RTX Spark silicon. The performance metrics of this machine are staggering for its form factor; it delivers up to one full petaflop of raw AI processing performance and boasts up to 128GB of unified system memory.

The strategic purpose of the Surface RTX Spark Dev Box is to enable developers to execute massive AI workloads locally without continuous reliance on the cloud. Microsoft stated that the device is fully capable of running colossal AI models containing up to 120 billion parameters natively on the local hardware. This makes the machine an unprecedented tool for high-intensity developer tasks such as local model fine-tuning, operating complex agentic AI workflows, and running demanding development pipelines that require zero-latency execution.

The Evolution of the Windows Platform

Microsoft explicitly focused on transforming Windows 11 into the premier environment for modern, AI-first software engineering, ensuring developers can choose seamlessly between local computing and the cloud. Several core Windows updates were announced to facilitate this:

  • Expanded Windows AI APIs: Empowering developers to integrate deeper system-level intelligence into their applications.
  • Native Coreutils: Microsoft is now making Linux-like command line utilities (Coreutils) run natively on Windows and broadly available to the public.
  • WSL Containers: Nearing public preview, this built-in utility provides a native way to create, orchestrate, and interact with Linux containers entirely through familiar CLI and API interfaces directly within Windows.
  • Intelligent Terminal: The command line experience has been reimagined with an Intelligent Terminal that intentionally brings context-aware assistance directly to the prompt.
  • Windows Development Skills: Now generally available, these tools grant autonomous agents the structured, programmatic knowledge required to build highly native Windows applications from end to end using WinUI3 skills alongside the WinApp CLI.
  • OpenClaw Support: Bringing native support for the open-source OpenClaw framework directly to the Windows operating system.

Furthermore, to manage this new agentic workforce securely, Microsoft introduced Windows 365 for Agents. This paradigm-shifting concept provides autonomous AI agents with their own fully managed Cloud PCs. This allows organizations to host, monitor, and provision compute resources for non-human workers just as they would for human employees. To augment local security, Microsoft Execution Containers were announced, bringing rigorous, OS-level isolation and containment to local agents running on a developer’s machine.

Conclusion

Build 2026 will be known as the point when Microsoft cemented itself in the conversation about what the real-world application of AI will look like.

By making such ambitious moves into enterprise applications directly challenging companies like Anthropic, Microsoft has declared its intentions. Microsoft IQ is a necessary layer of contextual data that provides agents with the essential foundation it needs, while the range of MAI models offer a wide range of performance tailored options for the developer community. The leaps in infrastructure and databases, ranging from Fabric to Rayfin and Azure HorizonDB, prove the building blocks are now in place for an agentic world, with an emphasis on a seamlessly integrated security layer including MDASH and Defender.

Add in the capabilities of the Discovery Engine to accelerate scientific research and the implications of the Majorana 2 quantum chip and the overall vision from Microsoft is clear: an entire ecosystem for intelligent computing designed for the modern developer who requires freedom to build and security of enterprise grade trust.

References

https://blogs.microsoft.com/blog/2026/06/02/microsoft-build-2026-be-yourself-at-work

https://venturebeat.com/technology/microsoft-ai-chief-says-company-was-set-free-from-openai-to-pursue-superintelligence

https://partner.microsoft.com/pt-pt/blog/article/microsoft-build-2026-recap

contact-centre, Customer-service

Bringing end-to-end visibility with screen recording in Dynamics 365 Contact Centre

Bringing end-to-end visibility with screen recording in Dynamics 365

(A unified capability for Dynamics 365 Customer Service and Dynamics 365 Contact Center that captures an agent’s on-screen workflow to provide context beyond just voice and text.)

Real-time User Journey

This journey illustrates how screen recording helps resolve a complex “process” dispute where a transcript alone wasn’t enough:

  1. Complex Interaction: An agent assists a customer with a high-value insurance claim. The interaction involves navigating three different internal legacy systems and a knowledge base.
  2. Triggered Recording: As soon as the agent accepts the call in the Contact Center, the screen recording starts automatically (or is manually toggled by the service rep).
  3. Visual Workflow: The agent hits a snag in the legacy system, leading to a delay. They search for a workaround in the knowledge base, which the recording captures.
  4. Secure Upload: Upon ending the session, the recording is automatically and securely uploaded to Microsoft Dataverse, linked directly to the specific conversation and case record.
  5. Quality Evaluation: A supervisor reviews the “Critical Failure” flagged by the Quality Evaluation Agent. While the transcript sounds professional, the Screen Recording shows the agent bypassed a mandatory compliance checkbox in the internal system.
  6. Targeted Coaching: The supervisor uses the video to show the agent exactly where they deviated from the process, using the recording as a visual training tool to prevent future errors.

Step-by-Step: How to Enable This Feature

Administrators can enable and govern this feature within the admin center settings:

  • Step 1: Admin Center Access

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

  • Step 2: Navigate to Recording Settings

Go to Operations > Insights > Call and Screen Recording.

  • Step 3: Enable Screen Recording Controls

Toggle the “Enable screen recording” switch to On. You can choose to enable this for “Voice Conversations” (automatic) and “Other Workloads” (manual toggle for agents).

  • Step 4: Configure Storage & Governance

Ensure your Dataverse storage is configured to handle video files. Set the Retention Policy (e.g., “Delete screen recordings after 90 days”) to align with your regional compliance laws.

  • Step 5: Set Role-Based Access (RBAC)

In the Security Roles section, assign the “Screen Recording Viewer” or “Manager” roles only to authorized supervisors and compliance officers. This ensures that sensitive on-screen data is protected.

  • Step 6: Deploy to Workspace

Go to Agent Experience Profiles and ensure the “Screen Recording” component is visible in the agent’s live conversation widget or productivity pane.

Infographic: Closing the Visibility Gap

AspectTranscript / Audio OnlyWith Screen Recording
VisibilityCaptures “What was said.”Captures “What was done.”
ComplianceHard to verify if policies were clicked.Visual proof of process adherence.
System UsageBlind to technical glitches.Identifies UI/UX bottlenecks in apps.
CoachingBased on verbal cues.Based on actual navigation and speed.
SecurityRedaction limited to text/audio.Role-based secure access to video files.

References

copilot-studio

Securing the Agentic Frontier: Addressing OWASP Top 10 Risks in Agentic AI with Microsoft Copilot Studio

This topic focuses on the governance and security framework required to protect “Autonomous Agents”—which have the power to act on behalf of users—against emerging threats like prompt injection, data exfiltration, and unauthorized tool use.

The 10 failure modes OWASP sees in agentic systems

  1. Agent goal hijack (ASI01): Redirecting an agent’s goals or plans through injected instructions or poisoned content.
  2. Tool misuse and exploitation (ASI02): Misusing legitimate tools through unsafe chaining, ambiguous instructions, or manipulated tool outputs.
  3. Identity and privilege abuse (ASI03): Exploiting delegated trust, inherited credentials, or role chains to gain unauthorized access or actions.
  4. Agentic supply chain vulnerabilities (ASI04): Compromised or tampered third-party agents, tools, plugins, registries, or update channels.
  5. Unexpected code execution (ASI05): Turning agent-generated or agent-invoked code into unintended execution, compromise, or escape.
  6. Memory and context poisoning (ASI06): Corrupting stored context (memory, embeddings, RAG stores) to bias future reasoning and actions.
  7. Insecure inter-agent communication (ASI07): Spoofing, intercepting, or manipulating agent-to-agent messages due to weak authentication or integrity checks.
  8. Cascading failures (ASI08): A single fault propagating across agents, tools, and workflows into system-wide impact.
  9. Human–agent trust exploitation (ASI09): Abusing user trust and authority bias to get unsafe approvals or extract sensitive information.
  10. Rogue agents (ASI10): Agents drifting or being compromised in ways that cause harmful behavior beyond intended scope.

Real-time User Journey: Secure Autonomous Execution

This journey illustrates how Copilot Studio’s security layers prevent an “Indirect Prompt Injection” attack:

  1. The Trigger: An autonomous agent is tasked with summarizing a set of incoming emails and syncing action items to a CRM.
  2. The Threat: One of the emails contains hidden malicious instructions (an “Indirect Prompt Injection”) designed to trick the agent into sending sensitive company data to an external personal email address.
  3. Real-time Interception: Before the agent executes the “Send Email” tool, the Microsoft Defender for Agents layer inspects the intent. It identifies that the destination address is not on the organization’s “Allow List” and that the payload contains sensitive keywords.
  4. Governance Block: The agent’s Managed Identity permissions are checked. The system realizes the agent is attempting an action (external exfiltration) that exceeds its scoped authority.
  5. Safe Resolution: The action is blocked. The user (and IT admin) receives a notification that a suspicious activity was intercepted, and the agent continues with other safe tasks.

Step-by-Step: How to Enable Security Features

To align your agents with the OWASP security recommendations using Copilot Studio tools:

  • Step 1: Assign a Managed Identity: Navigate to the agent settings in Copilot Studio and enable Microsoft Entra Agent ID. This ensures the agent has its own identity and doesn’t “ghost” as a high-privilege human user.
  • Step 2: Configure Content Safety: Under Settings > Security, enable Microsoft Azure AI Content Safety. Adjust the sliders to “High” for categories like Jailbreak detection and Protected Material.
  • Step 3: Define Tool Guardrails: In the Tools tab, for every connector (like SAP or Salesforce), set “User Confirmation” to “Required” for sensitive actions (e.g., deleting records or making payments).
  • Step 4: Enable Network Isolation: In the Power Platform Admin Center, configure Virtual Network (VNet) support for your environment to ensure agent traffic never leaves your private network.
  • Step 5: Monitor via Defender: Connect your agent logs to the Microsoft Defender for Cloud dashboard to receive real-time alerts on prompt injection attempts.

Infographic: OWASP Top 10 vs. Copilot Studio Protections

This table summarizes how Microsoft’s platform mitigates the most critical risks identified for LLM agents:

OWASP Risk CategoryCopilot Studio / Microsoft Security Solution
Prompt InjectionDefender for Agents: Scans inputs for malicious “jailbreak” patterns.
Insecure Output HandlingAzure AI Content Safety: Sanitizes agent responses before the user sees them.
Excessive AgencyScoped Managed Identities: Limits what an agent can do based on “Least Privilege.”
Data ExfiltrationDLP (Data Loss Prevention) Policies: Blocks sensitive data from being sent to unapproved domains.
Insecure Knowledge AccessTenant Graph Grounding: Respects existing SharePoint/OneDrive permissions automatically.

References

contact-centre, Customer-service

Seamless kickstart of Dynamics 365 Contact Centre

  1. Navigate to https://learn.microsoft.com/en-us/dynamics365/contact-center/implement/try-dynamics365-contact-center

2. Click “Try Dynamics 365 Contact Center”

3. Click “Try for free”. Pass your credentials and basic information to get provisioned for 1 month trial.

4. Once setup is done open “Power Platform admin center” –> Manage –> Environment –> Select the instance.

5. After opening the instance URL. Click “Create contact center”

6. It will take some time to configure and it will provide the URL as below

7. Click “Open contact center”

8. Configure “Chat” and it can be embedded in any website by just copying the code.

9. Click “Voice” to configure voice channel

10. Click “Conversation widget” it has code sample to embed in any other 3rd party system

11. Click “Representative experience profile” to manage representative experience profile.

12. Click “AI features” to configure AI features

13. Click “Reports” to manage and configure report setting.

This completes the basic setup of Dynamics 365 Contact Centre with minimum required channels.