This article is contributed. See the original author and article here.
Wave 3 marks a new version of Microsoft 365 Copilot, moving beyond assistance to embedded agentic capabilities.
The post Powering Frontier Transformation with Copilot and agents appeared first on Microsoft 365 Blog.
Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.
This article is contributed. See the original author and article here.
We’re excited to announce Copilot Cowork, the execution layer for Microsoft 365—delegate tasks, coordinate workflows, and stay in control.
The post Copilot Cowork: A new way of getting work done appeared first on Microsoft 365 Blog.
Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.
This article is contributed. See the original author and article here.
Customer expectations for service interactions continue to rise. They want conversations that are fast, accurate, and increasingly human.
Today, we’re excited to announce Custom Voice for Dynamics 365 Contact Center. It’s a major step forward in delivering more natural, personalized voice experiences across AI-powered customer interactions with as little as 50 voice samples!
Custom Neural Voices enable organizations to move beyond generic text-to-speech and create voice experiences that reflect their brand, values, and customer promise—while still benefiting from the scalability and intelligence of AI-driven contact centers.
Voice remains one of the most trusted and emotionally rich channels for customer engagement. Whether resolving an issue, providing updates, or guiding customers through self-service journeys, voice interactions shape how customers perceive your brand.
Every interaction with a customer is an opportunity to reinforce your brand. With Custom Voices, organizations can ensure their voice interactions match the tone, pacing, and personality customers expect. Voices are calm and supportive, confident and professional, or warm and conversational, enabling richer interactions across automated and agent-assisted workflows.
By combining advanced neural speech synthesis with Azure AI capabilities and native integration into Dynamics 365 Contact Center, organizations can now offer voice interactions that are:
Within Dynamics 365 Contact Center, Custom Neural Voices can be used across scenarios such as:
Voice is personal, and with that comes responsibility. Custom Neural Voices are developed and deployed with a strong emphasis on ethical use, transparency, and consent. They are only offered on a limited basis for verified customers and valid use cases. Microsoft’s responsible AI framework guides how these capabilities are offered. This helps organizations use advanced voice technology in ways that respect users and build confidence in AI-driven experiences.
Custom Neural Voices for Dynamics 365 Contact Center represents a significant evolution in how organizations think about voice automation. Rather than treating voice as a transactional tool, this capability makes it a strategic part of the overall customer experience. An experience that is intelligent, expressive, and aligned with the brand.
Learn more: Set up inbound calling for the voice channel | Microsoft Learn
The post Introducing Custom Voice for Dynamics 365 Contact Center appeared first on Microsoft Dynamics 365 Blog.
Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.
This article is contributed. See the original author and article here.
Global ERP environments are under increasing pressure. Regulatory requirements continue to evolve, compliance processes are moving to digital channels, and authorities expect structured electronic reporting delivered in prescribed formats and on local timelines. At the same time, IT teams are responsible for keeping ERP platforms current, reducing custom code, and supporting expansion into new markets without increasing operational complexity.
Dynamics 365 ERP applications are built to support these needs through comprehensive localization capabilities and extensible, upgrade-safe tools. As part of our ongoing investment, we are introducing localization for Türkiye. This addition expands Microsoft’s out-of-the-box localization coverage to 58 countries and regions, helping organizations address local regulatory requirements while maintaining a consistent, standardized ERP platform.
Globalization Studio is the extensibility framework in Dynamics 365 ERP apps for configuring and extending localization-related functionality without extensive custom development. It provides a consistent set of tools and services to support financial, tax, and regulatory processes while maintaining application upgradeability.
Key capabilities of Globalization Studio include:
This approach allows organizations to manage localization at the legal entity level while maintaining a common application foundation across regions. It also provides partners with a consistent framework for delivering additional localized functionality.
With the 2025 Release Wave 2, Dynamics 365 ERP introduces built-in localization for Türkiye. This release expands Microsoft’s country and regional coverage and provides a supported starting point for organizations operating in the Turkish market.
The Türkiye localization is built using Microsoft Globalization Studio tools and services and works across Dynamics 365 ERP applications. It follows Microsoft localization patterns and is designed to support updates as local regulatory requirements evolve.
For organizations operating in Türkiye, or planning future expansion, this localization can reduce the need for custom-built solutions or separate localization add-ons. From an IT perspective, this can support:
For partners, built-in localization provides a solid foundation for focusing on industry-specific or customer-specific requirements, rather than developing baseline regulatory functionality.
The Türkiye localization includes capabilities designed to address common regulatory and operational scenarios, including:
These capabilities are designed to help organizations meet local reporting and operational requirements when using Dynamics 365 ERP apps in Türkiye.
Localization functionality in Dynamics 365 ERP apps operates at the legal entity level. To enable Türkiye localization:
Once enabled, Türkiye-specific fields and user interface elements become available within the legal entity. For example, you can configure serial prefixes and enable continuous serial numbering of various documents, such as sales invoices or product receipts for purchase return orders.
You can also complete the monthly closing process by creating an e-Ledger journal and exporting an e-Ledger file in XBRL (eXtensible Business Reporting Language) format. Using the Globalization Studio’s Electronic Reporting tool, you can easily extend the format to meet your integrator’s requirements.
With this release, Dynamics 365 ERP apps continue to expand Microsoft’s localization footprint while maintaining a consistent approach to extensibility and upgradeability. Equipped with Globalization Studio tools, organizations can support operations across multiple countries and regions while addressing local requirements within a unified ERP platform.
The post Expanding global reach with Globalization Studio and new Türkiye localization in Dynamics 365 ERP appeared first on Microsoft Dynamics 365 Blog.
Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.
This article is contributed. See the original author and article here.
Twenty-five years ago, SharePoint set out to help people share knowledge and work better together, a mission that today operates at extraordinary scale.
The post SharePoint at 25: How Microsoft is putting knowledge to work in the AI era appeared first on Microsoft 365 Blog.
Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.
This article is contributed. See the original author and article here.
As enterprise workloads become more agentic, the expectations of ERP systems—and the teams that operate them—are shifting. Batch jobs, workflow orchestration, data import/exports, and background processes are no longer “just” technical plumbing–they are critical pieces of the operational fabric. They deliver timely financial results, accurate supply chain data, and reliable business intelligence driving process optimization.
To support this shift, observability needs to evolve beyond simple logs and reactive troubleshooting. Observability needs to provide meaningful insights into execution behavior, performance patterns, and operational context. This ensures IT teams can run ERP with confidence and reliability.
In Dynamics 365 ERP apps, we’ve long provided integration with Azure Application Insights to help organizations collect telemetry about user activity, failures, and application behavior. Now, with the expansion of batch telemetry signals — including start/stop events, failure data, throttling conditions, thread availability, and queue behavior — administrators and IT architects can gain deeper visibility into the health of critical batch-based workloads.
ERP observability historically focused on basic monitoring. It observed which jobs were running, whether a job failed, or whether alerts were triggered. These indicators are useful, but they lack operational context. Modern enterprise workloads are increasingly interconnected, and automation driven. Delays or failures in one workload can ripple outward, affecting downstream processes, reporting accuracy, and service delivery.
At the same time, teams are beginning to rely on AI agents to help monitor, diagnose, and in some cases suggest remediation steps. These tools need high-quality signals to be effective.
Batch workloads are a prime example. Batch jobs directly impact business outcomes, from overnight posting to inventory sync and settlements.
Without execution insights, teams guess root causes and waste time on manual investigation.
The monitoring and telemetry capabilities in Dynamics 365 ERP enable customers to send application telemetry to Azure Application Insights for analysis and alerting. The recent expansion of telemetry signals for batch workloads builds on this foundation by adding behavioral data specifically for batch execution patterns.
These signals include:
Emitting these signals into a customer-owned Application Insights resource means teams can apply their existing monitoring pipelines, dashboards, and alerting logic without changing how data is consumed.
Once batch telemetry data flows into Application Insights, teams can query it using Kusto Query Language (KQL) and build dashboards that correlate workload behavior with other operational metrics.
This richer observability enables several practical outcomes:
Here are some real‑world business scenarios that show how telemetry insights are helping customers troubleshoot issues and resolve problems faster.
A global consumer goods company frequently sees high priority jobs completing late. Batch Queue telemetry exposes queue congestion and thread exhaustion, showing when noncritical tasks bury priority workloads.
It helps surface when priority-based scheduling queues build up and delay time‑sensitive workloads, while also revealing misconfigured priorities that cause jobs to be processed out of order. It further enables teams to closely monitor queue health during cutover or high‑load events, ensuring critical workloads flow smoothly.
Similarly, a finance team’s bank reconciliation jobs remain “Waiting” for long periods. Thread telemetry reveals thread starvation—jobs were queued, but threads were fully consumed.
It helps explain why jobs remain stuck in a “Waiting” state by revealing when thread capacity is fully consumed by parallel workloads. It also highlights thread saturation patterns, enabling teams to right‑size AOS batch capacity for smoother, more predictable processing.
The expanded telemetry signals are not just a diagnostic tool. They serve as a foundation for smarter operations in an era where agents play an increasing role. High-fidelity Batch telemetry enables experiences like:
By making execution behavior more observable and actionable, Dynamics 365 ERP helps teams focus on outcomes, not just symptoms.
If you haven’t already configured monitoring and telemetry for your environment, the first step is to integrate your Dynamics 365 ERP instance with Azure Application Insights – refer. Monitoring and telemetry overview – Finance & Operations | Dynamics 365 | Microsoft Learn .
Once telemetry is configured, expanded batch signals can be toggled on from within system administration and begin flowing to your Application Insights pipeline for analysis.
Rich observability is a core requirement for running modern ERP workloads, especially as organizations adopt more automation and begin exploring agent-assisted operational tooling. By bringing deeper insight into batch execution behavior, our ERP portfolio apps in Dynamics 365 helps IT teams move from reactive troubleshooting toward proactive reliability and informed decision-making.
For more details visit Available telemetry – Finance & Operations | Dynamics 365 | Microsoft Learn.
The post Building Smarter Observability for Agentic ERP World using Dynamics 365 appeared first on Microsoft Dynamics 365 Blog.
Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.
Recent Comments