Dynamics 365 Business Central: Copy Sales and Purchase Line Descriptions (Type G/L Account) to G/L Entries
Hi, Readers.Today I would like to talk about how to copy Sales and Purchase Line Descriptions (Type G/L Account) to G/L Entries in Business Central. As you might know, you use general journals to post financial transactions to general ledger accounts and various other accounts. The other accounts include bank, customer, vendor, and employee accounts. […]
Published on: 5 hours ago
Python + Dataverse Series – #02 – use Datavese Web API using Python
Hi Folks, This is in continuation to the previous blog post…if you haven’t gone through the earlier post on connecting to Dataverse using Python, please have a look here Python + Dataverse Series – #01 – Console Application using Python Now, we will see how you can retrieve the records in Dataverse using Web API using … Continue reading "Python + Dataverse Series – #02 – use Datavese Web API using Python"
https://ecellorscrm.com/2025/07/03/python-dataverse-series-02-use-datavese-web-api-using-python/
Published on: 6 hours ago
Are you ready to Power Up at PPCC25?
https://www.youtube.com/watch?v=8D9KdG2YkLc
Published on: 10 hours ago
Copilot Studio: Part 1 – when automation bites back – autonomy ≠ chaos
Autonomy scares people. Not because they’re against AI. They’re against losing control, and rightly so. Most organizations aren’t afraid of what their Copilot Studio agent might do. They’re afraid of what it might do without asking. And yet, that’s the whole point of agents. If you need a human in the loop for every decision, you didn’t build an agent. You built a clunky wizard. Autonomy, done well, is not chaos. Autonomy, done well, is clarity. But clarity takes work. And most deployments skip that part.
[Sidenote: I hope you know this character:]
Autonomy is not a vibe
There’s a misconception that autonomy is a checkbox or a personality trait. As if some agents are independent and others are obedient. But autonomy isn’t about tone. It’s about timing, trust, and triggers. An autonomous agent doesn’t ask before it acts. It listens for signals. It builds a plan. It executes. Ideally, it also knows when to escalate. Not because you told it to in a script, but because it understood the stakes. That’s not advanced AI. That’s just responsible system design. Never heard about that? Might be a good idea to talk :-)
Agents don’t hallucinate: people hallucinate them
Here’s the uncomfortable truth: most agent hallucinations aren’t the model’s fault. They’re design failures. Someone told the agent it could retrieve knowledge and take action, but never clarified when to do which, or how to resolve conflicts between instructions and context.
The mess isn’t in the model. The mess is in the instructions we shipped and forgot to version.
[💡 So in case you haven’t talked to me in a while: everything is code and should be in source control for versioning and traceability.]
This is where autonomy becomes dangerous: not because the agent is too powerful, but because the environment around it is too fuzzy. No escalation logic. No fallback plans. No logging that anyone actually checks. It’s not that the agent acts alone. It’s that no one takes responsibility when it does.
Autonomy needs a job description
Want autonomy that doesn’t backfire? Treat your agents like new hires. They need
- Clear goals
- Explicit limits
- A decision framework
- Supervision that kicks in only when needed
In fact, the best mental model might be onboarding a junior colleague. You teach them how to handle 80% of cases. They ask for help on edge cases. Eventually, they escalate less because they’ve learned more. The difference? Your agents won’t magically learn unless you build for that too.
“Let’s start with retrieval” is how you stay stuck
Organizations love to “start simple.” Let’s build a retrieval agent. Let’s just do FAQs. Let’s just surface policy links. That’s fine—if the goal is to stall. Because retrieval agents don’t scale business value. They reduce helpdesk noise, maybe. But they don’t change how work gets done. The moment you want the agent to take action (submit a request, assign a case, file a report) you’ve stepped into task or autonomous territory. And if your architecture, data model, and governance aren’t ready? You’re back to waiting for a human to fix it.
Build trust into the agent, not around it
We don’t need to wrap every agent in disclaimers and safety rails. We need to build trust into the agent’s behavior. That means:
- Explainability: show users how the agent reached a conclusion
- Escalation: hand over control gracefully when the agent isn’t confident
- Containment: don’t let one bad action cascade across systems
- Auditability: store not just what the agent did, but why
Autonomy isn’t the enemy. It’s the maturity test. And right now, too many orgs are failing it.
Coming up next
- Part 0: Everything is an agent, until it isn’t
- Part 1: When automation bites back – autonomy ≠ chaos [📍 You are here]
- Part 2: Good agents die in default environments – ALM or bust to be published soon™️
- Part 3: The cost of (in)action – what you’re really paying for with Copilot Studio to be published soon™️
- Part 4: Agents that outlive their creators – governance, risk, and the long tail of AI to be published soon™️
- Part 5: From tool to capability – making Copilot Studio strategicto be published soon™️
https://m365princess.com/blogs/copilot1/
Published on: 11 hours ago
AI Agents Are Changing Software Forever—Are You Ready?
https://www.youtube.com/watch?v=9K7qcVW9j_s
Published on: 11 hours ago
Dynamics 365 Field Service : Launch related apps, including Dynamics 365 Remote Assist and Guides
In the fast-evolving world of field service management, empowering technicians with real-time, context-aware tools is key to boosting efficiency, accuracy, and customer satisfaction. Microsoft Dynamics 365 Field Service, a comprehensive solution for managing work orders, scheduling, and on-site service delivery, goes beyond traditional service software by integrating powerful mixed reality (MR) tools like Dynamics 365 Remote Assist and Dynamics 365 Guides.
In this article, let’s explore how these related apps are launched and used within Dynamics 365 Field Service to transform field operations.
Why Launch Related Apps from Field Service?
Field service technicians often encounter complex or unfamiliar scenarios that require expert input or step-by-step instructions. Instead of halting operations or waiting for assistance:
- Remote Assist enables real-time video calling and annotation, connecting field workers to remote experts.
- Guides offers interactive, hands-free instructions overlaid on real-world equipment using HoloLens or mobile devices.
- By launching these apps directly from Dynamics 365 Field Service, organizations create a unified, intelligent ecosystem that minimizes downtime and enhances service quality.
Dynamics 365 Remote Assist – Expert Help at Your Fingertips
What is it?
Dynamics 365 Remote Assist is a mixed-reality collaboration tool that allows field technicians to video call remote experts via Microsoft Teams while sharing what they see using HoloLens, a mobile phone, or a tablet.
How to Launch from Field Service?
1. Work Order Integration
When a technician opens a work order in the Field Service mobile app, they can access the “Remote Assist” button directly from the record. This context-aware link launches the Remote Assist app.
2. Single Sign-On and Deep Linking
The Remote Assist app launches automatically signed in using the same credentials and opens with the work order or asset information in context, avoiding duplicate data entry.
3. Real-Time Collaboration
Once connected, remote experts can see what the technician sees, annotate in real-time, and provide verbal guidance. They can even share documents, diagrams, and step-by-step procedures.
Benefits
- Faster issue resolution with expert guidance
- Reduced repeat visits
- Improved first-time fix rate
- Better training and upskilling of junior staff
Dynamics 365 Guides – Step-by-Step, Hands-Free Learning
What is it?
Dynamics 365 Guides is a mixed-reality training and assistance tool that overlays 3D instructions, videos, and text directly onto the equipment using Microsoft HoloLens or supported mobile devices.
How to Launch from Field Service?
1. Link to Asset or Task
Each work order or service task can include a link to a specific guide. The “Launch Guide” button opens the app and loads the relevant instructions for the technician.
2. Hands-Free Operation with HoloLens
Using voice commands or gestures, technicians can follow instructions while keeping their hands free to work on the equipment.
3. Data Sync with Field Service
Completion data or notes from Guides can be synced back into Dynamics 365 Field Service, maintaining a complete service history.
Benefits
- Reduces training time and cost
- Increases technician confidence and safety
- Standardizes repair and maintenance procedures
- Ideal for complex or regulated environments
Unified Experience: Bridging Apps with Context
- The real power lies in how these apps work together seamlessly within the Field Service ecosystem:
- Launching Remote Assist or Guides from a specific asset or work order
- Sharing device information, images, and technician location automatically
- Returning data (like completion status, photos, annotations) back into Dynamics 365 CE
All of this enables a closed-loop system of field data capture, expert collaboration, and proactive service delivery.
Security and Compliance
Both apps adhere to Microsoft’s enterprise-grade security and compliance standards. Data is encrypted in transit and at rest. Integration with Azure Active Directory ensures role-based access and SSO.
Final Thoughts
Launching related apps like Remote Assist and Guides directly from Dynamics 365 Field Service transforms how field service is delivered. It bridges the physical and digital, human and machine, remote and on-site—bringing true connected field service to life.
https://powerappbuilder.blogspot.com/2025/07/dynamics-365-field-service-launch.html
Published on: 12 hours ago
Use deep reasoning models for complex tasks | Power Platform Shorts
https://www.youtube.com/watch?v=lhvwSvG-fTo
Published on: 13 hours ago
Python + Dataverse Series – #01 – Console Application using Python
Hi Folks, This series is for Pro Code Developers especially those working on Dataverse and want to know how to work with Dataverse. I am starting this series as I see less content available in this area. This series will help you understand how to work with Dataverse using Python. So, in this post, first … Continue reading "Python + Dataverse Series – #01 – Console Application using Python"
https://ecellorscrm.com/2025/07/02/python-dataverse-series-01-console-application-using-python/
Published on: 14 hours ago
Azure SDK Release (June 2025)
Azure SDK releases every month. In this post, you'll find this month's highlights and release notes.
The post Azure SDK Release (June 2025) appeared first on Azure SDK Blog.
https://devblogs.microsoft.com/azure-sdk/azure-sdk-release-june-2025/
Published on: 14 hours ago
Scaling Attended Automations using Power Automate for Desktop
https://www.youtube.com/watch?v=PZiOdDvJc9I
Published on: 15 hours ago
Boost Dynamics Business Central with Private AI: Automated Invoice Processing
Introduction Manual invoice entry is nobody’s favorite part of BC activities. But what if you could hand off that grunt work to your own AI—one that runs entirely on your company’s servers, using open-source tools, with zero data ever leaving your network, and with zero licensing costs? In this post, I’ll walk through how I... Continue Reading →
Published on: 15 hours ago
Empower Your Marketers with Dynamics 365 Customer Insights and Copilot
https://www.youtube.com/watch?v=klUlqsDrxA8
Published on: 15 hours ago
2025 May DC Chapter Meeting
The recording is now up for the 2025 May DC Chapter Meeting! At this event, Daryl LaBar talked about TypeScript – what, why, and how! Why is TypeScript a big deal and why do you need to be here for it? Microsoft has been doing incredible work putting PowerFx all over the Power Platform, but … Continue reading 2025 May DC Chapter Meeting
The post 2025 May DC Chapter Meeting appeared first on Kylie Kiser.
https://kyliekiser.com/2025/07/02/2025-may-dc-chapter-meeting/
Published on: 17 hours ago
Knowledge sources vs Model Context Protocol (MCP): Which powers your Copilot Studio agent better?
As Copilot Studio continues to evolve, makers and developers are presented with increasingly powerful ways to extend their agents. Using Knowledge sources and/or the Model Context Protocol (MCP) offer distinct paths to enriching agent capabilities with data from different sources. But which one is right for your scenario? Knowledge sources offer a straightforward, no-code path for grounding
Published on: 18 hours ago
Track Time and Cost Savings with Power Automate’s New “Savings” (Preview) Feature
While creating a Power Automate flow, I discovered an exciting new feature called the “Savings” (Preview) feature in Power Automate. When I tried it, I found it very helpful for those looking to reduce costs by automating tasks with Power Automate flows instead of performing them manually. This feature helps you record exactly how much… Read More »
The post Track Time and Cost Savings with Power Automate’s New “Savings” (Preview) Feature first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.
Published on: 19 hours ago
Simplifying Copilot Chat in the Microsoft 365 Copilot app
Microsoft is simplifying Copilot Chat in the Microsoft 365 Copilot app for users without a Microsoft 365 Copilot license. Chat will now appear as the default module, making it easier to find. This change begins in early August 2025, with no admin action required. Based on your feedback, we’re simplifying the behavior of Copilot Chat in the Microsoft 365 Copilot app. This change only impacts users without a Microsoft 365 Copilot license. Today, the Pin Microsoft 365 Copilot Chat admin setting controls Copilot Chat entry points in Microsoft 365 apps, including the Microsoft 365 Copilot app across web, mobile, and desktop. Pinning is off by default, but users may be prompted to pin. We have heard from customers that this default experience creates confusion in the Microsoft 365 Copilot app. Users expect to see Copilot Chat but don’t know how to find it. To solve this, we are removing the Microsoft 365 Copilot app from the scope of the pinning setting. Instead, Chat will appear as the default module. Setting before and after this change: View image in new tab How this will affect your organization: There is no change for users with a Microsoft 365 Copilot license. When users without this license open the Microsoft 365 Copilot app, Chat will appear as the default module, with an entry point in the navigation menu. Microsoft 365 Copilot app for users without a Microsoft 365 Copilot license: While this change will help users discover Copilot Chat, these users have the choice to unpin Chat in their navigation bar. When this will happen: The rollout of this change begins early August 2025 and completes in the weeks following. View image in new tab Copilot Chat in the Microsoft 365 Copilot app will continue to honor other admin controls: Manage Microsoft 365 Copilot Chat | Microsoft Learn. What you need to do to prepare: No admin action is required. If you would like to inform users of this simplification, you could consider the following message: “Copilot Chat, Microsoft’s free and secure generative AI powered by GPT-4o, is now available in the Microsoft 365 […]
The post Simplifying Copilot Chat in the Microsoft 365 Copilot app appeared first on M365 Admin.
https://m365admin.handsontek.net/simplifying-copilot-chat-microsoft-365-copilot-app/
Published on: 21 hours ago
Microsoft Excel: Organization Data Types retire starting July 31, 2025
Organization Data Types in Microsoft Excel for Microsoft 365 will retire on July 31, 2025. Users should switch to Power BI or custom Excel add-ins. Existing data types will remain but won’t refresh. Bing data types are unaffected. For preparation, connect Excel to Power BI or explore custom add-ins. As announced in MC1072405 (May ’25), we’re retiring Organization Data Types in Microsoft Excel for Microsoft 365. This change simplifies the data types experience and encourages use of more robust, supported solutions like Power BI and custom Excel add-ins. When this will happen: This change will take effect on July 31, 2025. How this affects your organization: Starting July 31, 2025: Organization Data Types will be removed from the Data Types gallery on the Data ribbon tab in Excel. Users will no longer be able to convert values to new organization data types. Existing organization data types in workbooks will remain but will no longer refresh. This change does not affect Bing data types, which will continue to be supported. What you can do to prepare: If your users rely on Organization Data Types, we recommend: Connecting Excel to Power BI to access organizational data. Exploring custom add-in solutions using the Excel Data Types APIs. For guidance, refer to: Overview of data types in Excel add-ins Connect Excel to Power BI semantic models Message ID: MC1107494
The post Microsoft Excel: Organization Data Types retire starting July 31, 2025 appeared first on M365 Admin.
Published on: 21 hours ago
Retirement of Loop Component Rendering in Word for the Web
Support for rendering Loop components in Word for the web will be retired on September 1, 2025. Existing Loop components will display as read-only placeholders with links to open them externally. Organizations should notify users, update documentation, and encourage accessing Loop components via external links. No admin action is required. We’re retiring support for rendering Loop components in Word for the web, effective September 1, 2025. This change aligns the Word web experience with Word desktop, where Loop components are already displayed as read-only placeholders. When this will happen: This change will roll out automatically and take effect on September 1, 2025. How this affects your organization: Loop component creation in Word for the web was previously deprecated. With this update, existing Loop components will no longer render interactively in Word web documents. Instead, users will see a read-only placeholder with a link to open the Loop component externally. This ensures continued access to content without data loss but removes in-document interactivity. Our reporting indicates that your organization may have users who open Word web documents containing Loop components. No admin action is required, but this change may impact user workflows. What you can do to prepare: Notify your users about the upcoming change and the new placeholder experience. Update internal documentation to reflect the change in behavior. Encourage users to access Loop components via the provided external link if interactivity is needed. Message ID: MC1107493
The post Retirement of Loop Component Rendering in Word for the Web appeared first on M365 Admin.
https://m365admin.handsontek.net/retirement-loop-component-rendering-word-web/
Published on: 21 hours ago
Microsoft Teams: Compact notification size for users
Microsoft Teams is introducing a compact toast notification size for Windows users, available from July 2025. Users can enable it via Settings > Notifications > Choose Compact. This feature aims to reduce screen clutter and distractions. No admin action is required. We’re introducing a new compact toast notification size in Microsoft Teams for Windows. This update gives users the option to reduce the visual footprint of notifications, offering a cleaner, more minimalist experience that helps reduce screen clutter and distractions. This message is associated with Microsoft 365 Roadmap ID 496175. When this will happen: Targeted Release: Rolling out early July 2025, expected to complete by mid-July 2025. General Availability (Worldwide): Rolling out mid-July 2025, expected to complete by late July 2025. General Availability (GCC, GCC High, DoD): Rolling out late July 2025, expected to complete by late July 2025. How this will affect your organization: After this rollout, Windows users will be able to choose between the standard and compact toast notification sizes in Teams by navigating to: Settings > Notifications > Choose Compact This feature is off by default and must be enabled by the user. It is designed to improve focus and reduce screen clutter, especially in high-notification environments. View image in new tab What you need to do to prepare: No admin action is required. The feature will be available to all users once their Teams client updates to the supported build. There are no admin controls for this feature. You may consider notifying your users about this new option to help them tailor their notification experience. Message ID: MC1107491
The post Microsoft Teams: Compact notification size for users appeared first on M365 Admin.
https://m365admin.handsontek.net/microsoft-teams-compact-notification-size-users/
Published on: 21 hours ago
Reminder: Updates to required permissions for Microsoft Graph Beta API deviceManagement
Starting July 31, 2025, certain Microsoft Graph Beta APIs will require either DeviceManagementScripts.Read.All or DeviceManagementScripts.ReadWrite.All permissions. Previously, they required DeviceManagementConfiguration.ReadWrite.All or DeviceManagementConfiguration.Read.All. Update any apps, scripts, or tools accordingly. Detailed instructions are available in the provided links. As mentioned in MC1066336, starting July 31, 2025, or soon after, the following Graph APIs will require either DeviceManagementScripts.Read.All or DeviceManagementScripts.ReadWrite.All permissions to continue working: ~/deviceManagement/deviceShellScripts ~/deviceManagement/deviceHealthScripts ~/deviceManagement/deviceComplianceScripts ~/deviceManagement/deviceCustomAttributeShellScripts ~/deviceManagement/deviceManagementScripts How this will affect your organization: Previously, these Graph APIs required granting either DeviceManagementConfiguration.ReadWrite.All or DeviceManagementConfiguration.Read.All permissions. If you have any enterprise applications, scripts or other tools that have been granted these permissions they will need to be updated in order to continue calling the listed Graph APIs. What you need to do to prepare: Ensure any apps, scripts, or tooling that reference the listed Graph APIs include either DeviceManagementScripts.Read.All or DeviceManagementScripts.ReadWrite.All permissions and remove the old permissions: DeviceManagementConfiguration.ReadWrite.All or DeviceManagementConfiguration.Read.All. For detailed instructions for updating permissions for applications, refer to: Update an app’s requested permissions in Microsoft Entra ID If you are an independent software vendor or partner with an application deployed in your customer environments that needs updating, review Grant consent for the added permissions for the enterprise application Message ID: MC1107490
The post Reminder: Updates to required permissions for Microsoft Graph Beta API deviceManagement appeared first on M365 Admin.
Published on: 21 hours ago
Microsoft Dataverse – Use Dataverse table data as knowledge in Copilot agents
We are announcing the ability to use Dataverse tables as a knowledge source for agents in Microsoft Dataverse. This feature will reach general availability on July 31, 2025. How does this affect me? You can now add your CRM data, including data from Microsoft Dynamics 365 applications, as knowledge sources for your declarative agents and copilot agents. With a simple add process you can ensure that your agents are grounded in your enterprise knowledge. What action do I need to take? This message is for awareness and no action is required. If you would like more information on this feature, please visit Use Dataverse table data as knowledge in Copilot agents. Message ID: MC1107451
The post Microsoft Dataverse – Use Dataverse table data as knowledge in Copilot agents appeared first on M365 Admin.
Published on: 21 hours ago
Hotpatching now enabled by default for new Windows quality update policies
Newly created Windows quality update policies now have hotpatch updates enabled by default to streamline policy creation. When will this happen: This feature is now available for all Windows Autopatch users. How this will affect your organization: Organizations using Windows Autopatch will benefit from faster security compliance and reduced downtime for devices running supported Windows editions. What you need to do to prepare: Create your new Windows Autopatch quality update policies today, with hotpatch enabled by default, to ensure your organization starts receiving hotpatches as early as August 2025. For new policies, hotpatch updates will be enabled by default. Just review and deploy them as usual. To create a new quality update policy, follow the steps here: Go to the Microsoft Intune admin center. Navigate to Devices > Windows updates > Quality updates. Select Create, and select Windows quality update policy. Under the Basics section, enter a name for your new policy and select Next. Under the Settings section, “When available, apply without restarting the device (“Hotpatch”) will be set to Allow. Select the appropriate Scope tags or leave as Default. Then, select Next. Assign the devices to the policy and select Next. Review the policy and select Create. To enable hotpatch updates on your existing quality update policies, follow the steps here: Go to the Microsoft Intune admin center. Navigate to Devices > Windows updates > Quality updates. Select the quality update policy you wish to modify. A new screen with its properties will appear. Select Edit in the “Settings” section. Under “Automatic update deployment” settings, locate the option “When available, apply without restarting the device (“hotpatch”).” Toggle it to Allow. Additional information: Learn about hotpatch updates for Windows 11. Learn how to enroll devices to receive hotpatch updates. Read Windows Autopatch documentation. Message ID: MC1107364
The post Hotpatching now enabled by default for new Windows quality update policies appeared first on M365 Admin.
Published on: 21 hours ago
Microsoft Copilot Studio – Publish agents to WhatsApp
We are announcing the ability to publish agents to WhatsApp in Copilot Studio. This feature will reach general availability on July 31, 2025. How does this affect me? The WhatsApp channel will be made available in Copilot Studio. When publishing an agent to WhatsApp, Copilot Studio fetches your WhatsApp configuration from Azure Communication Services and lets you choose where your agent should appear. What action do I need to take? This message is for awareness and no action is required.If you would like more information on this feature, please visit the Publish agents to WhatsApp article. Message ID: MC1107311
The post Microsoft Copilot Studio – Publish agents to WhatsApp appeared first on M365 Admin.
https://m365admin.handsontek.net/microsoft-copilot-studio-publish-agents-whatsapp/
Published on: 21 hours ago
Dynamics 365 Contact Center – Use enhanced disposition code capabilities
We are announcing new disposition code functionality which will enable more configurability in indicating the outcome of a voice or chat conversation in Dynamics 365 Contact Center. This feature will reach general availability on July 31, 2025. How does this affect me? The enhancements of disposition codes help customer service representatives save time and resources in indicating how calls end. Customer service representatives can choose from a predetermined list while supervisors can view these codes in the closed conversation summary form to aggregate data on how calls are going for their representatives. Customer service representatives will have the ability to choose a category that will filter the available disposition codes. If the administrator has enabled a maximum number of disposition codes allowed, customer service representatives will see the number displayed in the disposition code area. What action do I need to take? This message is for awareness and no action is required. Message ID: MC1107207
The post Dynamics 365 Contact Center – Use enhanced disposition code capabilities appeared first on M365 Admin.
Published on: 21 hours ago