This article is contributed. See the original author and article here.
Today, we’re announcing the first pricing update for Microsoft Dynamics 365 in more than five years. Since our last pricing update, Dynamics 365 has transformed customer relationship management (CRM) and enterprise resource planning (ERP) processes with connected applications across lines of business—from marketing, sales, customer and field service, to finance, operations, and supply chain—and each year, we release hundreds of new features and enhancements designed to help people work smarter, reclaim time, and collaborate seamlessly.
While a lot has changed in the world in the last five years, our vision has stayed true: ensuring the Dynamics 365 experience helps organizations adapt to change and proactively transform their business. We have delivered on this through innovations that have helped organizations supercharge customer experiences with AI-powered, real-time customer insights for marketers, sellers, and service agents; as well as by optimizing operations and mission-critical processes with data insights, supply chain visibility, and end-to-end automation of financial processes. And today, we are seeing organizations of all sizes across industries benefit from Microsoft Copilot in Dynamics 365.
As we look ahead, our commitment to our customers is to continue to offer the most value and highest return on your investment in business applications, helping to fuel digital transformation.
The price changes will be effective October 1, 2024, and the products will be priced comparably across different currencies. The full list of Dynamics 365 products for which prices are being updated can be found here. Cloud pricing for Microsoft Dynamics 365 Business Central will remain unchanged.
This article is contributed. See the original author and article here.
Today, we’re announcing the first pricing update for Microsoft Dynamics 365 in more than five years. Since our last pricing update, Dynamics 365 has transformed customer relationship management (CRM) and enterprise resource planning (ERP) processes with connected applications across lines of business—from marketing, sales, customer and field service, to finance, operations, and supply chain—and each year, we release hundreds of new features and enhancements designed to help people work smarter, reclaim time, and collaborate seamlessly. You can read the official Dynamics 365 blog post here.
Below is the list of products for which prices are being updated with effect from October 1, 20241:
Product
Price before October 1, 2024
Price as of October 1, 20242
Microsoft Dynamics 365 Sales Enterprise
$95
$105
Microsoft Dynamics 365 Sales Device
$145
$160
Microsoft Dynamics 365 Sales Premium
$135
$150
Microsoft Microsoft Relationship Sales3
$162
$177
Microsoft Dynamics 365 Customer Service Enterprise
$95
$105
Microsoft Dynamics 365 Customer Service Device
$145
$160
Microsoft Dynamics 365 Field Service
$95
$105
Microsoft Dynamics 365 Field Service Device
$145
$160
Microsoft Dynamics 365 Finance
$180
$210
Microsoft Dynamics 365 Supply Chain Management
$180
$210
Microsoft Dynamics 365 Commerce
$180
$210
Microsoft Dynamics 365 Human Resources
$120
$135
Microsoft Dynamics 365 Project Operations
$120
$135
Microsoft Dynamics 365 Operations – Device
$75
$85
Prices for Dynamics 365 on-premises customer engagement and operations products will increase by the same percentage as the respective cloud versions. Pricing for cloud products not listed above, such as Microsoft Dynamics 365 Business Central, will remain unchanged.
These increases will apply globally to new and existing customers (upon renewal as of October 1, 2024), and the products will be priced comparably in other currencies. To comply with local regulations, US government list prices for the same products will increase by 10% effective October 1, 2024, followed by another smaller increase effective October 1, 2025, to bring parity with commercial pricing outlined above.
1 All prices are per user per month (or per device per month where noted). 2 Prices shown are for informational purposes only and may not be reflective of actual list price due to currency, country, region, and variant factors. Contact a Microsoft sales representative for additional information on pricing. 3 Pricing per user per month will increase by $15 in all tiers in Microsoft Relationship Sales. Only 10-99 user tier shown for simplicity.
This article is contributed. See the original author and article here.
One of the biggest takeaways is that AI reinvention is a whole new way of working that involves both software and culture. It’s a cultural shift. Microsoft Viva empowers leaders and organizations to make that shift. We’re excited to announce new capabilities to help drive enterprise-wide adoption of Copilot, including the general availability of Microsoft Copilot Dashboard and Microsoft Copilot Academy, powered by Viva, which will be available to all Copilot for Microsoft 365 customers.
This article is contributed. See the original author and article here.
We are excited to announce the general availability (GA) of Elastic Jobs for Azure SQL Databases.
Elastic Jobs is a fully integrated Azure SQL database service that allows you to automate and manage administrative tasks across multiple SQL databases in a secure, scalable way. It can run one or more T-SQL job scripts in parallel using Azure portal, PowerShell, REST, or T-SQL APIs. Jobs can be run on a schedule or on-demand, targeting any tier of Azure SQL Database. Job target can include all databases in a server, in an elastic pool, across multiple servers and even databases across different subscriptions and geo regions on Azure. Servers and pools are dynamically enumerated at runtime, so jobs run against all databases that exist in the target group at the time of execution.
Where can you use Elastic Jobs?
Any database administration or management job that can be scripted with a T-SQL script is a good candidate for elastic jobs. Some of these example scenarios include:
Automate management tasks like deploy schema changes, index rebuilding, performance/telemetry data collection etc.
Configure jobs like query execution, collecting results across a collection of databases on a recurring basis.
Aggregate and collect data for processing and reporting.
Data movement, ETL processing to extract/process/insert data between tables in a database.
.. to name a few.
What are some significant capabilities of Elastic Jobs?
Elastic Jobs makes it easy and secure to manage large number of SQL databases across Aure. Some significant security and management capabilities of Elastic Jobs include:
Microsoft Entra ID (formerly Azure Active Directory) support for central administration of authentication and permissions
Service-managed Private Link support to securely connect to target databases.
Integration with Azure Alerts for job execution status notification.
Easily scale Job Agent’s tier to connect to hundreds of target databases concurrently across Azure.
Dynamic enumeration target databases in target servers and elastic pools
Jobs can be composed of multiple steps to customize the execution sequence.
All functionalities can be accessed through portal, PowerShell, T-SQL and REST APIs
How do you setup and use Elastic Jobs?
Setting up and using elastic jobs is simple as described here.
Job Agent and Job database creation
Job Agent and associated Job database creation experience in portal is similar to a SQL database creation. As part of job agent creation, its service tier can be chosen, and a user assigned managed identity can be added for Entra authentication. Once the job agent is created, its portal page allows easy access to all its capabilities.
Defining Jobs, their target groups and monitoring them through job agent’s portal page.
Jobs and job steps can be defined, edited and executed through portal page. These jobs can also be scheduled to run at regular intervals and their execution can be monitored.
Advanced security functionalities, alert notification and scaling are also easily accessed through Job Agent’s portal page.
Job agents Entra ID can be changed and private links to target databases established easily through portal page. Azure Alerts can be defined for getting alert notification on job executions status. Scaling the job agent’s compute tier to enable it to connect to hundreds of target databases concurrently is also easy through portal page links.
Steps described above for creating, configuring, and managing elastic jobs also be accomplished through using PowerShell, REST and T-SQL APIs.
Pricing
Billing for Job agents will start at GA time, April 11th, 2024. Billing cards in the Azure portal page will show estimated cost based on the provisioned job agent tier.
*Billing for the job agents in national clouds are expected to start a little later, depending on the billing pipeline deployment in those regions.
Regional availability
The Elastic Jobs is available in all the regions that Azure SQL Database is available.
This article is contributed. See the original author and article here.
The Copilot analytics report within Dynamics 365 Customer Service provides a good overview of the usage of Copilot features by agents. You can derive insights into the most frequently leveraged features, impact of Copilot on agent productivity, and agent satisfaction with Copilot responses. While this report provides a good summarization of the impact Copilot has on contact center KPIs, we are seeing interest from customers to drill into individual interaction data, especially around the interactions voted as negative by their agents.
This blog provides an overview of the underlying data that powers the Copilot dashboard, and the additional data points available to you. We hope that with this context, you can use model customization to modify these reports to better suit your organization’s needs.
First, make sure your organization is storing agent experience data. You can ask your admin to validate this for you in the Customer Service admin center by making sure they select the Agent experience data checkbox in Copilot help pane. You can continue using Copilot with this setting turned off, but you won’t have historical interaction data to build analytics.
View and analyze agent experience data
When you turn on agent experience data, Dataverse stores the following:
Transcripts from when agents chat with Copilot
Agent actions such as copying a summary presented or using a suggested reply from Copilot
Agent feedback on responses in the form of thumbs up, thumbs down and verbatim feedback
You can use the transcript id stored in msdyn_interactioncontext to get the full transcript of this interaction from the msdyn_copilottranscriptdata entity.
Interaction 2: Agent provides feedback on Copilot’s responses
The agent wasn’t fully satisfied with Copilot’s response and is choosing to rate the response with a thumbs down and provides verbatim feedback.
Another entry in msdyn_copilotinteraction gets created with the same msdyn_scenariorequestid and msdyn_scenariotype, but with msdyn_interactiontypename set to “ThumbsDown”.
You can use the reference msdyn_interactiondataid to gather the verbatim feedback the agent provided from the msdyn_copilotinteractiondata entity.
Interaction 3: Agent asks Copilot to summarize a case
The agent picks up a case from a colleague and requests Copilot to generate a summary to catch up.
Another entry in msdyn_copilotinteraction gets created with a new msdyn_scenariorequestid and msdyn_scenariotype set to “Case summary”.
You can use the reference msdyn_interactiondataid to retrieve the summary that was generated from the msdyn_copilotinteractiondata entity.
Interaction 4: Agent uses Copilot to write an email
Agent decides to leverage Copilot to generate an email with troubleshooting steps using write an email feature. They request an email of type “Resolve the customer’s problem”.
Another entry in msdyn_copilotinteraction gets created with a new msdyn_scenariorequestid and msdyn_scenariotype set to “Write an email”.
You can use the reference msdyn_interactiondataid to retrieve the email that was generated, along with the knowledge sources used from msdyn_copilotinteractiondata entity .
Recent Comments