<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dynamic Monk on Medium]]></title>
        <description><![CDATA[Stories by Dynamic Monk on Medium]]></description>
        <link>https://medium.com/@DynamicsMonkmarketing?source=rss-bb2d7dbad27f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*x3BAxvi1knv_et4Wm6HfBg.png</url>
            <title>Stories by Dynamic Monk on Medium</title>
            <link>https://medium.com/@DynamicsMonkmarketing?source=rss-bb2d7dbad27f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 01:05:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@DynamicsMonkmarketing/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Dynamics 365 Year-End Change Freeze: What to Lock Before December | Dynamics Monk]]></title>
            <link>https://medium.com/@DynamicsMonkmarketing/dynamics-365-year-end-change-freeze-what-to-lock-before-december-dynamics-monk-0cf697102f63?source=rss-bb2d7dbad27f------2</link>
            <guid isPermaLink="false">https://medium.com/p/0cf697102f63</guid>
            <category><![CDATA[dynamics-365-for-finance]]></category>
            <dc:creator><![CDATA[Dynamic Monk]]></dc:creator>
            <pubDate>Thu, 19 Nov 2026 05:47:17 GMT</pubDate>
            <atom:updated>2026-11-19T05:47:17.324Z</atom:updated>
            <content:encoded><![CDATA[<p>Picture a group running Dynamics 365 Finance across India, the UAE and Singapore. It is 19 December, the office is half empty, and bank statements have stopped arriving in the ledger. The IT lead checks the change log and finds nothing, because nothing was changed.</p><p>The integration’s sign-in secret expired that morning. Someone set it up two years ago, has since left, and never wrote the date down. Finance spends Christmas week keying in bank lines by hand.</p><p>The freeze worked. It just guarded the wrong door.</p><p>A year-end change freeze in Dynamics 365 is a window, usually from early December to mid-January, in which nothing changes in the live system without an emergency sign-off. It protects the close only if it covers three things: what your team changes, what Microsoft changes, and what simply runs out.</p><p>Most plans cover the first and stop. The other two are where December goes wrong.</p><h3>Microsoft does not take December off</h3><p>Your freeze is an internal agreement. Microsoft is not part of it. Finance and Operations, Business Central and the Power Platform all keep updating on their own schedules, and an update that lands on 20 December changes your system as surely as a deployment would.</p><p>So the real decision is a simple one. Either take the next update early, in November, and test your close against it while your team is still around. Or pause it and take it after the freeze.</p><p>Both have a cost. Pausing feels safer, but the skipped update does not go away. It arrives in February alongside the next one, and your testing has to cover two sets of changes at once. Taking it early means more work in November, when everyone is already busy preparing for the close.</p><p>If your close relies on custom code around posting, tax or bank settlement, pausing is usually worth the bigger February test. If it does not, take the update early and freeze on a version you have already tested.</p><p>Either way, write the version number into the freeze plan. If you cannot name the version you are protecting, you are not really protecting it.</p><p>One more thing to settle here. A freeze covers a whole environment, not a single company within it. If your Indian entities share an environment with your UAE and Singapore entities, a December freeze also freezes India, which closes its year on 31 March and may have plans for December. Agree that before 1 December, not on the 15th.</p><h3>Set up January in November</h3><p>The best freezes have one habit in common: anything that has to change on 1 January is set up weeks earlier with a start date, so it switches on by itself. Nobody has to log in on New Year’s Day.</p><p>Tax is the clearest example. Dynamics 365 lets every tax rate carry a start date and an end date. A rate that changes on 1 January can be entered in November and will apply on the day without anyone touching the system during the freeze.</p><p>The bigger date this year belongs to the UAE. Businesses there with revenue of AED 50 million or more must issue e-invoices from 1 January 2027, which lands right in the middle of most freeze windows. That leaves two honest choices: finish the connection and testing before December, or name it in the freeze plan as a planned exception, with its own sign-off and a way back if it fails.</p><p>The ledger calendar needs the same care. Open the 2027 periods before December. Then agree who controls the December period, because Dynamics 365 offers two ways to stop posting and they are not the same. On hold can be undone. Closed cannot. A December period closed a week too early means every late adjustment has to be pushed into January and explained to the auditors. Keep December on hold until the auditors are done.</p><p>Finally, run the year-end close once in a test environment, on a copy of real data, before the freeze starts. Most groups run it more than once as late adjustments come in. Better to learn how a second run behaves in November than on 3 January.</p><h3>What expires while everyone is away</h3><p>This is the door from the opening story, and the one most plans leave open. Nothing here is a change anyone makes, so it never appears on a change list. It just has a date, and the date does not care about the holidays.</p><p>The usual suspects are easy to name:</p><ul><li>Sign-in secrets and certificates that let integrations, e-invoicing and bank feeds talk to Dynamics 365. They are set up with an expiry date, and the date is often two years out.</li><li>Automations that run as a person. A Power Automate flow built under an employee’s account stops when that person leaves, changes role or resets their password.</li><li>Scheduled jobs set to end on 31 December. They stop exactly as configured, and the first anyone hears of it is a missing report in January.</li><li>Subscription renewals. A licence renewal that falls inside the freeze locks in user numbers for another term, which we explored in our comparison of EA, CSP and MCA-E.</li></ul><p>The fix is unglamorous. Before 1 December, list everything that expires before the end of January, give each line an owner and a date, and renew it now, while the people who understand it are still at their desks. A list without owners is just a schedule of future incidents.</p><h3>Leave one door open in your Dynamics 365 year-end change freeze</h3><p>A freeze with no way out does not stop change. It pushes change out of sight, where nobody records it.</p><p>Start by deciding what the freeze does not cover. New customers, suppliers and bank accounts are day-to-day business and must keep flowing. Approval rules, user permissions, tax settings and integrations are frozen. Name the grey areas in the plan, because the person deciding at 6 pm on 23 December should not be interpreting a policy document.</p><p>Then make the emergency route something people can actually use. That means at least two named approvers, with their leave dates checked against the window. Every fix is tested first in a copy of the live system on the same version, which is why that version number matters. And the approver hears, before saying yes, whether the change can be undone.</p><p>Every emergency change gets reviewed in January. The ones that keep recurring belong on next year’s November list.</p><h3>Common failure modes</h3><ul><li>The freeze stops deployments, not people. Releases are paused, but administrators still adjust workflows and permissions directly in the live system. The warning sign is changes in the audit log with no request behind them.</li><li>The test system runs ahead of the live one. Microsoft often updates test environments first, so an emergency fix is tested on a different version from the one it goes into. The warning sign is a version number that does not match the plan.</li><li>December is closed instead of put on hold. Late adjustments then have to be forced into January. The warning sign is a period status changed by someone outside the close team.</li><li>The only approver is on a beach. The emergency route exists on paper and nobody can use it. The warning sign is a single name in the approver column.</li></ul><p>None of these is a technology failure. Each starts as a gap in the plan that was there to be seen in November.</p><h3>Conclusion</h3><p>A good year-end freeze is mostly done before it starts. Decide on Microsoft’s next update, set up every 1 January change with a start date, list and renew everything that expires, and make sure someone with authority is actually reachable over the break. Then December can be as quiet as it is meant to be.</p><p>Dynamics Monk works with Dynamics 365 teams across India, the UAE and Southeast Asia, and this is the list worth working through before the first of December.</p><p><em>Originally published at </em><a href="https://www.dynamicsmonk.com/blog/dynamics-365-year-end-change-freeze"><em>https://www.dynamicsmonk.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0cf697102f63" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dynamics 365 Licensing: EA vs CSP vs MCA-E Cost Comparison | Dynamics Monk]]></title>
            <link>https://medium.com/@DynamicsMonkmarketing/dynamics-365-licensing-ea-vs-csp-vs-mca-e-cost-comparison-dynamics-monk-4bab80a9db3d?source=rss-bb2d7dbad27f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bab80a9db3d</guid>
            <category><![CDATA[dynamics-365]]></category>
            <dc:creator><![CDATA[Dynamic Monk]]></dc:creator>
            <pubDate>Thu, 19 Nov 2026 05:44:55 GMT</pubDate>
            <atom:updated>2026-11-19T05:44:55.865Z</atom:updated>
            <content:encoded><![CDATA[<p>When an enterprise evaluates Dynamics 365, licensing discussions usually begin with the number of users, the applications they need and the features required. However, another decision can have a significant impact on the overall cost of ownership: how the organisation purchases its Microsoft subscriptions.</p><p>An organisation can procure Dynamics 365 through an Enterprise Agreement (EA), a Cloud Solution Provider (CSP) partner or a Microsoft Customer Agreement for Enterprise (MCA-E). Although the underlying Dynamics 365 product may be the same, the commercial structure, billing arrangements, purchasing flexibility and financial commitments can differ.</p><p>For organisations deploying Dynamics 365 Finance, Supply Chain Management or Customer Engagement applications across multiple business units, these differences deserve attention before the first subscription is purchased.</p><p>The right billing route is not necessarily the one with the lowest quoted licence price. It is the one that aligns subscription costs with actual usage, procurement requirements and the organisation’s growth plans.</p><h3>Understanding the Three Dynamics 365 Purchasing Routes</h3><p>Before comparing costs, it is important to distinguish between a licensing model and a purchasing agreement. Dynamics 365 licensing determines what users can access and what functionality they are entitled to use. The purchasing agreement determines the commercial arrangement through which those subscriptions are acquired and billed.</p><h3>1. Enterprise Agreement (EA)</h3><p>An Enterprise Agreement is a volume licensing arrangement designed primarily for larger organisations making a multi-year commitment to Microsoft technologies.</p><p>For commercial customers, the traditional EA is generally structured around a three-year term and has a minimum requirement of 500 users or devices for new agreements. It provides negotiated pricing, predictable annual payments and an established process for reconciling additional licensing requirements.</p><p>One important feature is the annual true-up process. Organisations can account for additional eligible users, devices and services during the agreement period, rather than treating every increase as a separate procurement exercise.</p><p>For an enterprise implementing Dynamics 365 across several legal entities, this structure can support centralised purchasing and financial planning.</p><p>However, a three-year commitment requires accurate forecasting. If an organisation overestimates its licensing requirements, it risks carrying costs for subscriptions that are not being fully utilised.</p><h3>2. Cloud Solution Provider (CSP)</h3><p>The Cloud Solution Provider programme allows organisations to purchase Microsoft cloud subscriptions through an authorised Microsoft partner.</p><p>Under this arrangement, the partner can manage subscription procurement, billing and, depending on the engagement, technical support and other services. The customer generally receives its invoice from the CSP partner rather than directly from Microsoft.</p><p>CSP is particularly relevant for organisations that want a partner involved beyond the initial licensing transaction.</p><p>Dynamics 365 subscriptions purchased through CSP are subject to the applicable subscription terms and commercial rules. Under Microsoft’s New Commerce Experience (NCE), for example, subscription duration, renewal dates and cancellation conditions influence how much flexibility a customer has after purchasing.</p><p>Customers may have options involving monthly or annual billing, depending on the product, subscription term and available commercial terms. Importantly, monthly billing does not necessarily mean a monthly cancellable commitment. An annual subscription billed monthly can still carry a commitment for the full annual term.</p><p>This distinction matters when an organisation experiences changes in project scope, workforce size or implementation timelines.</p><h3>3. Microsoft Customer Agreement for Enterprise (MCA-E)</h3><p>The Microsoft Customer Agreement (MCA) is a cloud-focused purchasing agreement that provides a more flexible alternative to traditional volume licensing arrangements. Its enterprise purchasing route is commonly referred to as MCA-E.</p><p>Unlike the traditional Enterprise Agreement, MCA does not require a three-year purchasing commitment or a minimum purchase quantity. Organisations can acquire Microsoft cloud services, including Dynamics 365, under a streamlined agreement with flexible billing arrangements.</p><p>For enterprise customers, MCA-E offers a centralised commercial relationship with Microsoft, supported by billing accounts and billing profiles. These profiles help organisations organise subscriptions, manage invoice information and allocate financial responsibility across departments or business units.</p><p>The agreement can support direct purchasing through Microsoft. Depending on the purchasing arrangement, customers may also work with a Microsoft partner.</p><p>One consideration is that flexibility in purchasing does not automatically translate into lower subscription costs. Organisations still need to evaluate negotiated pricing, subscription terms, payment frequency and their expected consumption.</p><p>For businesses moving from an existing EA, the transition also requires attention to billing administration, subscription ownership and financial reporting. The commercial agreement may change without requiring a complete Dynamics 365 implementation or tenant migration.</p><h3>How the Billing Route Changes Total Cost of Ownership</h3><p>The difference between EA, CSP and MCA-E becomes more meaningful when organisations examine the costs beyond the advertised price per user.</p><p>Several factors influence the actual financial outcome.</p><h3>1. Negotiated pricing and commercial discounts</h3><p>Enterprise Agreements can offer volume-based pricing and negotiated commercial terms. However, organisations should not assume that every Dynamics 365 subscription automatically receives a lower price under EA.</p><p>The final commercial benefit depends on the agreement, eligible products, negotiated discounts and applicable pricing conditions.</p><p>CSP pricing is influenced by the partner’s commercial arrangement and the price offered to the customer. Partners may provide additional services, licensing guidance or bundled support, which should be evaluated separately from the subscription price.</p><p>MCA-E offers a direct commercial relationship with Microsoft for eligible enterprise customers. Pricing and discounts depend on the negotiated terms rather than simply the agreement name.</p><p>When comparing quotations, organisations should examine the actual net subscription price, not just the standard list price.</p><h3>2. Subscription commitments and unused licences</h3><p>Subscription duration has a direct impact on financial flexibility.</p><p>Consider an organisation implementing Dynamics 365 Finance for 300 employees. During the initial rollout, it purchases 300 user subscriptions, expecting all departments to go live within six months.</p><p>However, the implementation is delayed, and only 210 employees are actively using the system.</p><p>The organisation is now paying for 90 subscriptions that are not yet contributing to business operations.</p><p>Under CSP NCE, an annual subscription billed monthly generally remains a full-year commitment. After the applicable seven-day cancellation window, reducing or cancelling the subscription is restricted until the next renewal, subject to the applicable product terms.</p><p>A monthly-term subscription provides greater cancellation flexibility, but its commercial pricing may differ.</p><p>With MCA, organisations should review the specific subscription terms and billing arrangements before committing. Under an EA, the applicable enrollment and subscription structure determine how quantities can be adjusted.</p><p>The key consideration is to align subscription purchases with implementation milestones rather than projected headcount alone.</p><h3>3. Billing frequency and cash flow</h3><p>The frequency of payment can affect cash flow even when the total subscription commitment remains unchanged.</p><p>For example, an annual subscription with monthly billing distributes payments across the year. An annual subscription paid upfront requires a larger initial cash outflow.</p><p>This distinction is particularly relevant for organisations managing multiple Dynamics 365 applications.</p><p>A company deploying Finance, Supply Chain Management and Customer Service may have different implementation schedules for each application. Aligning subscription purchases and payment cycles with those schedules can improve budget management.</p><p>EA supports annual payment arrangements across its traditional three-year structure. CSP NCE offers different billing frequencies depending on the subscription term and product eligibility. MCA billing arrangements also depend on the subscription and purchasing configuration.</p><p>Finance teams should therefore evaluate both the total contractual commitment and the timing of cash outflows.</p><h3>A Practical Scenario: Choosing a Billing Route for Dynamics 365</h3><p>Consider a manufacturing enterprise implementing Dynamics 365 Finance and Supply Chain Management across multiple locations.</p><p>The organisation has 600 employees, operates through four legal entities and expects its workforce to expand as additional facilities become operational.</p><p>Its purchasing decision should consider the following:</p><ul><li>Enterprise Agreement: Worth evaluating if the organisation has an existing EA relationship, qualifies for the relevant commercial structure and can benefit from negotiated terms, predictable commitments and centralised procurement.</li><li>CSP: Worth evaluating if the organisation requires partner-led licensing management, ongoing support and flexibility to select subscription terms that match deployment requirements.</li><li>MCA-E: Worth evaluating if the organisation prefers a cloud-focused commercial agreement, direct Microsoft engagement and centralised billing administration without a traditional three-year EA commitment.</li></ul><p>There is no universally cheaper option in this scenario. The result depends on negotiated pricing, subscription quantities, deployment timelines and the additional services included in each commercial proposal.</p><h3>Common Cost Considerations Before Selecting an Agreement</h3><p>A purchasing decision should account for more than the initial licence quotation.</p><p>Technical and finance teams should jointly validate:</p><ul><li>User licensing: Identify the correct base and attach licences based on actual user roles and application requirements.</li><li>Subscription quantities: Separate immediate deployment requirements from future implementation phases.</li><li>Contractual commitments: Review renewal dates, cancellation restrictions, minimum terms and provisions for reducing subscriptions.</li><li>Additional capacity: Account for Dataverse storage, database capacity, environments and other applicable add-ons.</li><li>Azure consumption: Include hosting, integration services, data storage and other consumption-based resources where applicable.</li><li>Support costs: Distinguish Microsoft product support from partner-managed services, implementation support and ongoing administration.</li><li>Financial administration: Review invoice consolidation, currency, tax treatment, purchase orders and internal cost allocation.</li></ul><p>These considerations are particularly important for organisations running multiple Dynamics 365 applications alongside Power Platform and Azure services.</p><h3>How to Make the Right Purchasing Decision</h3><p>Before selecting a billing route, organisations should prepare a licensing and cost assessment covering at least the expected deployment period.</p><p>A useful assessment should include three elements.</p><p>First, establish the licensing baseline. Map users to their actual responsibilities, determine the appropriate Dynamics 365 licences and identify where attach licences or additional capacity may be applicable.</p><p>Second, model different commercial scenarios. Obtain comparable quotations for EA, CSP and MCA-E wherever the organisation is eligible. Evaluate annual expenditure, total contractual commitments, payment frequency and renewal exposure.</p><p>Third, forecast changes in demand. Account for employee growth, phased deployments, acquisitions, seasonal workforce changes and potential application expansion. A purchasing route that works for the current user count may not remain commercially appropriate three years later.</p><p>Importantly, licensing decisions should involve IT, procurement and finance teams. Technical teams understand application requirements, procurement evaluates commercial terms, and finance assesses budget commitments and cost allocation.</p><h3>Conclusion</h3><p>Choosing between Enterprise Agreement, CSP and MCA-E is not simply a procurement decision. It influences how an organisation commits to Microsoft subscriptions, manages billing, accommodates changing user requirements and forecasts its technology expenditure.</p><p>EA can provide commercial predictability for qualifying large organisations. CSP can introduce partner-led purchasing and licensing management. MCA-E provides a cloud-focused agreement with flexible purchasing and billing administration.</p><p>The most effective approach is to compare the total cost of the proposed licensing arrangement against actual business requirements, rather than selecting an agreement based on its headline discount.</p><p>For enterprise Dynamics 365 deployments, the right commercial structure should support the implementation roadmap, not create additional financial commitments around it.</p><p><em>Originally published at </em><a href="https://www.dynamicsmonk.com/blog/dynamics-365-enterprise-agreement-csp-mca-e-cost"><em>https://www.dynamicsmonk.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bab80a9db3d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dynamics 365 Multi-Country Rollout: UK, UAE, Singapore | Dynamics Monk]]></title>
            <link>https://medium.com/@DynamicsMonkmarketing/dynamics-365-multi-country-rollout-uk-uae-singapore-dynamics-monk-82b5a4f83541?source=rss-bb2d7dbad27f------2</link>
            <guid isPermaLink="false">https://medium.com/p/82b5a4f83541</guid>
            <category><![CDATA[dynamics-365]]></category>
            <dc:creator><![CDATA[Dynamic Monk]]></dc:creator>
            <pubDate>Thu, 19 Nov 2026 05:43:00 GMT</pubDate>
            <atom:updated>2026-11-19T05:43:00.307Z</atom:updated>
            <content:encoded><![CDATA[<p>Consider a UK-headquartered group that has approved a global Dynamics 365 Finance template. Four months into design, the UAE finance lead asks which provider will transmit invoices from 1 January 2027, and the Singapore team asks whether its data can sit in a UK-hosted environment. Neither question was in the plan, and both change the go-live order.</p><p>A Dynamics 365 rollout across the UK, UAE and Singapore rarely stalls because of the software. It stalls when the sequence follows internal convenience while tax authorities and residency rules run on their own calendars.</p><h3>Let the regulatory calendar set the sequence</h3><p>All three countries are moving to structured e-invoicing built on Peppol, on different timelines.</p><ul><li>UAE: Under Ministerial Decision 244 of 2025, businesses with revenue of AED 50 million or more appoint an accredited service provider by 31 July 2026 and issue e-invoices from 1 January 2027. Smaller businesses appoint by 31 March 2027 and start on 1 July 2027. Guidelines are still being revised, and version 2.0 appeared in October 2026.</li><li>Singapore: GST InvoiceNow applies to new voluntary GST registrants from 1 April 2026. Existing registrants follow in phases between April 2028 and April 2031, and IRAS notifies each business of its date.</li><li>UK: All VAT invoices in B2B and B2G transactions must be e-invoices from 1 April 2029. HMRC published its roadmap at Budget 2026, with legislation planned in Finance Bill 2026–27.</li></ul><p>The UAE has the shortest runway and the UK the longest. That does not mean the UAE goes live first. It means UAE tax design must be settled early.</p><h3>A sequence that holds up in practice</h3><h3>Phase 1: Template and first entity</h3><p>Build the shared design first: chart of accounts, financial dimensions, intercompany rules, master data standards and security roles. Go live with the entity closest to the design authority, often the UK, so template defects surface while the stakes are manageable. Keep country logic in legal entity configuration, not in the template.</p><h3>Phase 2: UAE, with e-invoicing as a gating item</h3><p>Treat the service provider as a project dependency, not a late integration task. Appoint the provider, confirm which invoices and credit notes must flow through it, and test the UAE Peppol format before user acceptance testing. Microsoft has announced Peppol-based e-invoicing for Finance and Operations in the UAE, so confirm availability for your version, along with the add-in, Azure Key Vault and Blob Storage requirements.</p><h3>Phase 3: Singapore</h3><p>With GST at 9% and later InvoiceNow dates for existing registrants, Singapore can follow once the template has proven itself twice. Check whether the Singapore Peppol format is covered natively by the Electronic invoicing service or needs a partner solution. Microsoft publishes coverage by country.</p><h3>Tax configuration across three regimes</h3><p>Each legal entity needs its own sales tax setup, covering tax codes, tax groups and item tax groups, with Electronic reporting handling formats. Standard rates are the easy part (UK VAT 20%, UAE VAT 5%, Singapore GST 9%). The harder differences are tax invoice content, credit note rules, reverse charge on imported services and the tax effect of intercompany recharges. A management fee from the UK to the Singapore entity, for instance, raises GST and transfer pricing questions that a global template cannot answer alone. Bring local tax advisers into design, not into user acceptance testing.</p><h3>Data residency: decide before provisioning</h3><p>Finance and Operations environments are deployed to a chosen geography, and Microsoft documents which regions are data resident. Microsoft now describes residency through macro regions: the UK and UAE sit in Europe, UK, Middle East and Africa, and Singapore sits in Asia-Pacific. Customers with Finance or Supply Chain Management and 20 or more paid licences can select a specific region at environment creation. New customers also cannot create Lifecycle Services projects since February 2026, so environments are managed through the Power Platform admin center.</p><p>The real decision is one shared environment or one per geography. A shared environment simplifies consolidation and intercompany processing but places every entity’s data in one macro region. Separate environments respect local boundaries more closely, at higher integration and reporting cost. Legal and security teams should review the choice against UK GDPR, Singapore’s PDPA, UAE data protection law and any sector rules before the architecture is fixed.</p><p>Align the Electronic invoicing service with the environment, since it can be deployed in UK, Asia and UAE Azure geographies. Geo-to-geo migration exists, but features missing in the target geography stop working after the move, so check parity first.</p><h3>Common challenges</h3><ul><li>Provider onboarding: contracting and certification take longer than planned, and test windows are short.</li><li>Master data: missing tax registration numbers and Peppol identifiers for customers and vendors block invoices at go-live.</li><li>Group reporting: separate environments need a deliberate consolidation model and refresh approach.</li></ul><p>Because guidelines in all three countries are still moving, keep a regulatory change log owned by finance, not only by IT.</p><h3>Conclusion</h3><p>Sequence by regulatory clock and operational risk, not by revenue or reporting line. Settle UAE tax design early, prove the template in the first entity, use Singapore as the confirmation wave, and decide data residency before any environment is provisioned.</p><p>Dynamics Monk works across the UK, UAE and Singapore, and these are the questions worth answering before the first environment is created.</p><p><em>Originally published at </em><a href="https://www.dynamicsmonk.com/blog/dynamics-365-rollout-uk-uae-singapore-sequencing-tax-data-residency"><em>https://www.dynamicsmonk.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82b5a4f83541" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Supplier Communications Agent in Dynamics 365: Master Data Guide | Dynamics Monk]]></title>
            <link>https://medium.com/@DynamicsMonkmarketing/supplier-communications-agent-in-dynamics-365-master-data-guide-dynamics-monk-3f3800ec3274?source=rss-bb2d7dbad27f------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f3800ec3274</guid>
            <category><![CDATA[dynamics-365]]></category>
            <dc:creator><![CDATA[Dynamic Monk]]></dc:creator>
            <pubDate>Thu, 19 Nov 2026 05:41:10 GMT</pubDate>
            <atom:updated>2026-11-19T05:41:10.118Z</atom:updated>
            <content:encoded><![CDATA[<h3>1. The problem starts before the supplier sends an email</h3><p>A procurement manager at a manufacturing company issues 150 purchase orders to suppliers across multiple regions. Within a few days, the procurement inbox starts filling up. One supplier confirms an order but changes the delivery date. Another requests a price revision. A third sends a revised quantity in a PDF attachment, while several suppliers have not confirmed their purchase orders at all.</p><p>The procurement team must identify which purchase order each email refers to, verify the requested changes, update the relevant records and inform production or inventory teams if delivery commitments are affected.</p><p>This is the kind of repetitive work that Microsoft’s Supplier Communications Agent, part of the Procurement Agent in Dynamics 365 Supply Chain Management, is designed to reduce.</p><p>The agent uses AI to analyse incoming supplier emails, identify purchase order references, recognise confirmations and change requests, and extract information such as revised quantities, prices and delivery dates. It can also prepare follow-up emails for unconfirmed or delayed purchase orders.</p><p>However, introducing this capability raises an important question: can the existing Dynamics 365 environment reliably identify the supplier, match the communication to the correct purchase order and interpret the information being exchanged?</p><p>If supplier records contain outdated email addresses, purchase orders use inconsistent units of measure, or delivery commitments are not maintained accurately, automation becomes more difficult to manage. This makes master data preparation an important part of implementing supplier communication automation in Dynamics 365.</p><h3>2. Understanding the Supplier Communications Agent in Dynamics 365</h3><p>The Supplier Communications Agent is a capability within Microsoft’s Procurement Agent for Dynamics 365 Supply Chain Management. It uses AI to process routine supplier communications and reduce the manual effort involved in managing purchase order confirmations, revisions and follow-ups.</p><p>Supplier communication traditionally depends on email exchanges between buyers and vendors. Even organisations using electronic data interchange (EDI) for regular transactions may still receive important updates through email, particularly when suppliers need to explain delays, request changes or provide supporting documents.</p><p>The Procurement Agent addresses this gap by connecting supplier communication with purchasing records in Dynamics 365.</p><h3>2.1 Inbound supplier communication</h3><p>The agent can analyse incoming supplier emails and determine their procurement context. It identifies whether a message relates to a purchase order confirmation, a quantity adjustment, a price revision, a cancellation or a change in delivery commitment.</p><p>For example, when a supplier requests an increase in the ordered quantity, the agent can identify the purchase order reference, locate the relevant information and present the proposed change to the procurement team.</p><p>It can also interpret delivery information when suppliers provide an estimated shipping date instead of a warehouse arrival date. Using relevant transit-time assumptions, the agent can help determine the expected arrival date.</p><p>This reduces the need for buyers to manually search through email threads and compare every supplier response against the original purchase order.</p><h3>2.2 Outbound supplier communication</h3><p>The agent also supports communication initiated by the procurement team.</p><p>When a supplier has not confirmed a purchase order within a defined period, the agent can identify the outstanding confirmation and prepare a reminder. Similarly, when a delivery is overdue, it can generate a follow-up requesting an updated delivery commitment.</p><p>Depending on the configuration, these emails can be saved as drafts for human review or sent automatically.</p><p>The objective is not to remove procurement oversight. It is to reduce the time spent identifying routine communication requirements and preparing responses.</p><p>Microsoft also provides an Impact Analysis capability within the broader Procurement Agent. When enabled, it evaluates how supplier-requested changes could affect inventory, production schedules and customer deliveries. This helps buyers assess the operational consequences before accepting a change.</p><h3>3. Why supplier master data is the first thing to address</h3><p>Supplier master data is the structured information that identifies a vendor and defines how the organisation conducts business with that vendor.</p><p>In Dynamics 365 Supply Chain Management, supplier records are maintained through vendor accounts and related procurement and financial configurations. Depending on the business structure, supplier information may also be maintained across multiple legal entities.</p><p>For the Supplier Communications Agent, this information provides the context needed to interpret supplier messages and connect them with purchasing transactions.</p><p>Consider a supplier who sends an email requesting a delivery-date revision. For the agent to process this request correctly, the system needs to establish which supplier sent the email, which purchase order the message concerns, which purchase order line is being changed, what the original commitment was and what the supplier is proposing instead.</p><p>These questions depend on more than AI’s ability to interpret natural language. They also depend on the quality and consistency of the underlying business records.</p><p>A useful implementation approach is to review the following master data areas before enabling automated supplier communication.</p><h3>4. Five master data areas to review before enabling the agent</h3><h3>4.1 Vendor account details and contact information</h3><p>The vendor account is the starting point for supplier identification in Dynamics 365 Supply Chain Management. Each supplier should have a unique and correctly mapped vendor account, with updated registered names, addresses and contact details. Particular attention should be given to supplier email addresses, as these determine how procurement-related communication is managed.</p><p>Suppliers may have separate contacts for purchase order confirmations, delivery updates, invoice queries and general commercial communication. Maintaining these distinctions helps procurement teams direct messages to the appropriate contacts. Dynamics 365 supports multiple contact records against a vendor, with specific purposes assigned to each. For the Supplier Communications Agent, the Purchase Order Communications contact purpose is particularly relevant when configuring supplier follow-ups.</p><p>Vendor status and applicable holds should also be reviewed to ensure that inactive or restricted suppliers are not treated as regular procurement contacts. Organisations operating across multiple legal entities should check for duplicate vendor accounts and inconsistencies in supplier information between entities. These checks establish a reliable supplier record that the agent can use when processing incoming emails and preparing outbound communication.</p><h3>4.2 Purchase order references and transaction accuracy</h3><p>The Supplier Communications Agent works with purchase order information to identify supplier commitments and requested changes.</p><p>Consider a supplier sending the following response:</p><p>“Regarding PO 45001234, we can supply 500 units instead of the originally agreed 600. The remaining quantity will be available next week.”</p><p>The agent needs to identify the relevant purchase order, locate the affected line and interpret the proposed quantity change. This becomes difficult when purchase order references are inconsistent across email threads, attachments and internal records.</p><p>Organisations should therefore review how purchase orders are created, communicated and maintained. Purchase order numbers must be shared accurately with suppliers, while line-level information should clearly identify the products, quantities and delivery commitments involved.</p><p>The status of each purchase order is equally important. Draft, approved, confirmed and revised orders represent different stages of the procurement process. Maintaining these distinctions helps buyers understand whether a supplier response relates to an active purchasing commitment.</p><p>Purchase order change management also requires attention. Dynamics 365 supports approval workflows for purchase order modifications, allowing organisations to define how changes are reviewed before they become part of an approved transaction.</p><p>For example, a supplier’s request to increase a unit price should not automatically become an approved commercial change simply because the revised amount was extracted correctly. The procurement team must evaluate the request against contractual terms, purchasing policies and approval requirements before applying the change.</p><h3>4.3 Item master data and units of measure</h3><p>Unit-of-measure inconsistencies are a common source of confusion in procurement transactions.</p><p>Consider a purchase order that specifies 100 individual components. The supplier responds that it can deliver 10 boxes, with each box containing 10 components. The quantities are equivalent, but the supplier and buyer are expressing them differently.</p><p>For an automated communication process, this distinction matters. The system must interpret the supplier’s response in the context of the purchasing unit and the item being ordered.</p><p>Dynamics 365 Supply Chain Management supports product-specific units of measure and unit conversions. The purchasing unit is typically derived from the released product’s purchasing unit configuration, although it can be changed on an individual purchase order line.</p><p>The Supplier Communications Agent can recognise different unit representations, such as packs versus individual units, and identify the intended quantity change. However, this does not eliminate the need for accurate item master data.</p><p>Organisations should ensure that product and released product records are correctly identified, purchasing units are configured appropriately and conversion factors accurately reflect supplier packaging arrangements. Vendor-specific product references and descriptions should also be consistent with the information used in purchase orders and supplier correspondence.</p><p>For example, if a supplier sells an item in cartons of 12 but the purchasing unit is maintained as individual pieces, the conversion must accurately reflect that relationship. Incorrect conversion factors can create discrepancies between the supplier’s commitment and the organisation’s expected receipt quantity.</p><h3>4.4 Delivery dates, transit assumptions and receiving locations</h3><p>Supplier communication is not limited to quantities and prices. Delivery commitments are equally important because they influence inventory availability, production planning and customer fulfilment.</p><p>A supplier may provide an estimated shipping date rather than a confirmed warehouse delivery date. For example, the supplier might communicate an estimated time of departure (ETD) of 12 November, with an expected transit period of eight days. The procurement team needs to understand that the estimated time of arrival (ETA) would be 20 November, subject to the applicable transit assumptions.</p><p>The Procurement Agent can recognise shipping-date information and help derive an estimated arrival date using agreed transit-time assumptions. This makes delivery-related configuration important when preparing the Dynamics 365 environment.</p><p>Procurement and supply chain teams should ensure that requested and confirmed delivery dates are maintained accurately, vendor-specific lead times reflect actual supply arrangements and receiving site and warehouse information are correctly configured. Delivery calendars and working-day assumptions should also be considered when calculating expected arrival dates.</p><p>It is equally important to understand the current boundaries of the agent. For example, Microsoft’s documentation identifies changing the delivery site for a specific purchase order line as an unsupported supplier communication scenario. A supplier requesting a different warehouse or receiving site therefore requires manual review rather than an assumed automated update.</p><p>This distinction is particularly relevant for organisations operating multiple warehouses or manufacturing locations, where a delivery change can affect inventory allocation and production schedules.</p><h3>4.5 Supplier records across legal entities and vendor relationships</h3><p>Organisations operating across multiple legal entities often maintain supplier relationships at different levels. A supplier may work with several business units, supply different product categories or operate through separate registered entities.</p><p>If supplier information is duplicated or maintained inconsistently, procurement teams may struggle to establish a consistent view of the relationship.</p><p>Dynamics 365 Supply Chain Management traditionally supports vendor records maintained within individual legal entities. Microsoft’s newer Supplier Engagement capability introduces a more centralised approach to supplier onboarding and supplier information management across legal entities.</p><p>Announced in August 2026 as a public preview, Supplier Engagement introduces global vendor management, allowing organisations to maintain a shared supplier record across multiple legal entities. Supplier information, including contacts, addresses, certifications and organisational details, can be maintained centrally and shared where appropriate. Once qualified, suppliers can be released into one or more legal entities for operational transactions.</p><p>It is important not to confuse this capability with the Supplier Communications Agent. They address different parts of supplier management. Supplier Engagement focuses on supplier onboarding, lifecycle information and collaboration, while the Supplier Communications Agent focuses on purchase order-related email communication and follow-ups.</p><p>Together, they represent a broader direction towards connected supplier management in Dynamics 365.</p><h3>5. How the Supplier Communications Agent uses this information</h3><p>Once the master data and procurement configurations have been reviewed, organisations can assess how the agent fits into their purchasing workflow.</p><p>Consider a supplier requesting a change to an existing purchase order. The process begins when the supplier sends an email containing the relevant purchase order reference and the proposed change. The agent analyses the message, identifies its procurement context and extracts the relevant information.</p><p>It then uses the available supplier and purchase order information to match the communication with the relevant transaction and purchase order line. The buyer can review the original values alongside the supplier’s proposed changes.</p><p>If Impact Analysis is enabled, the broader Procurement Agent can evaluate the potential consequences for inventory, production schedules and customer deliveries. This gives the procurement team additional context before making a decision.</p><p>The buyer then determines whether the requested change can be accepted and applies the approved modification through the appropriate procurement process.</p><p>The important distinction is that the agent supports information extraction, matching and decision preparation. It does not make every supplier-requested change an automatically approved transaction.</p><p>This workflow becomes more dependable when the underlying vendor, item and purchase order information is accurate.</p><h3>6. Dynamics 365 technical prerequisites for implementation</h3><p>Master data preparation is only one part of implementation. The Supplier Communications Agent also requires the correct application versions, integrations, identities and mailbox configurations.</p><h3>6.1 Application and feature requirements</h3><p>Microsoft’s current setup documentation specifies Dynamics 365 Supply Chain Management version 10.0.44 or later, with all available quality updates. The environment must also have Copilot for finance and operations apps version 1.0.03048.2 or later and Copilot in Microsoft Dynamics 365 Supply Chain Management version 1.1.03510.1 or later.</p><p>The relevant capabilities must be enabled through Feature Management, including Immersive Home, Agent management and Procurement Agent — Supplier Communications. Organisations planning to enable automatic follow-up emails must also activate the corresponding optional feature separately.</p><p>Microsoft currently identifies the Supplier Communications Agent as a production-ready preview. This distinction is important for organisations evaluating the feature for deployment, as production-ready preview capabilities remain subject to Microsoft’s supplemental terms and may have documentation or functionality changes.</p><h3>6.2 Microsoft Entra ID and security configuration</h3><p>The agent requires a dedicated identity to connect with the services it uses. This identity is configured through Microsoft Entra ID and must have the appropriate permissions to interact with Dynamics 365 Supply Chain Management, Microsoft Dataverse, Microsoft Copilot Studio and Exchange.</p><p>The deployment process includes assigning the required product licenses and security roles to the agent identity. Users responsible for managing agent configurations and reviewing agent results also require appropriate permissions in Dataverse and Supply Chain Management.</p><p>Organisations should avoid using an ordinary employee account as a substitute for a properly configured agent identity. A dedicated identity makes access management, permission control and ongoing maintenance easier to govern.</p><h3>6.3 Mailbox integration and email synchronization</h3><p>Supplier communication depends on reliable email connectivity. The organisation must configure at least one mailbox and establish server-side synchronization between the email server and Dataverse.</p><p>Both shared and private mailboxes are supported, subject to their respective ownership and access requirements. Shared mailboxes can be associated with a team in the Power Platform environment, while private mailboxes are associated with individual users.</p><p>For automatic follow-up emails, additional email configuration is required, including the Microsoft Graph email provider and relevant application credentials.</p><p>This is also where supplier contact master data becomes important. The organisation must ensure that the configured mailboxes can receive and process supplier correspondence and that the vendor records contain valid communication details. Microsoft specifically recommends disabling automatic follow-up emails in sandbox environments where purchase order information may be outdated or vendor email addresses may be missing.</p><h3>6.4 Copilot Studio agent availability</h3><p>The setup process also requires the relevant Microsoft Copilot Studio agents to be published. These include Supplier communications Agent — inbound and Supplier Communications Agent — outbound.</p><p>The deployment wizard generally handles the publishing process automatically. However, data loss prevention (DLP) policies can affect agent publishing and connector availability. Administrators should therefore review the relevant Power Platform environment policies and confirm that the required connections are permitted before deployment.</p><h3>7. A practical approach to preparing Dynamics 365 for supplier communication automation</h3><p>Implementing AI in procurement should not begin with enabling every available feature. It should begin with identifying where existing procurement processes are inconsistent.</p><p>The first step is to review supplier master data, including vendor account numbers, contact information, registered addresses, vendor status and legal entity relationships. Duplicate records and outdated communication details should be addressed before the agent is connected to procurement mailboxes.</p><p>The next step is to examine purchase order structures and transaction practices. Purchase order numbering, line-level product information, confirmation status and approval workflows should be consistent. Procurement teams should also establish how supplier-requested changes are reviewed and applied, particularly when they affect prices, quantities or delivery commitments.</p><p>Item and delivery configurations require similar attention. Purchasing units, unit conversions, vendor lead times, transit assumptions and warehouse information should reflect actual procurement arrangements. These details provide the transaction context required to interpret supplier communications accurately.</p><p>Once the data foundation is reviewed, administrators can configure the required identities, security roles, mailboxes, server-side synchronization and Copilot Studio connections. The agent can then be tested using representative supplier communications, including purchase order confirmations, quantity revisions, price requests and delivery delays.</p><p>A controlled rollout is preferable to enabling automatic email sending immediately. Procurement teams can initially review generated drafts and proposed changes, assess how accurately the agent identifies purchase orders and extracts supplier requests, and investigate recurring exceptions.</p><p>As confidence improves, organisations can evaluate automatic follow-ups for suitable scenarios while retaining appropriate approval controls for commercial and operational changes.</p><h3>8. What supplier communication automation means for procurement teams</h3><p>The value of the Supplier Communications Agent extends beyond reducing the number of emails procurement professionals need to write. It changes how purchasing teams identify and respond to supplier-related exceptions.</p><p>Instead of spending time checking which vendors have not responded, buyers can review purchase orders that require attention. Instead of manually comparing every supplier email against an existing order, they can review the changes identified by the agent.</p><p>When Impact Analysis is enabled, teams can also evaluate the potential consequences of delivery and quantity changes for inventory, production and customer commitments. This creates a more informed approach to managing supplier-related exceptions.</p><p>However, these improvements depend on the quality of the information connecting suppliers, purchase orders and operational processes.</p><p>A supplier communication agent cannot compensate for a vendor account containing incorrect contact details. It cannot reliably resolve a purchasing-unit conversion that has been configured incorrectly. Nor can it make an unapproved commercial change acceptable simply by extracting it accurately.</p><p>This is why master data management should be treated as an implementation priority rather than a post-deployment clean-up activity.</p><h3>Prepare the data before automating the communication</h3><p>The Supplier Communications Agent in Dynamics 365 Supply Chain Management offers procurement teams a practical way to reduce repetitive supplier correspondence and improve visibility into purchase order confirmations and changes.</p><p>Its capabilities become particularly useful when supplier communication is connected to accurate vendor records, consistent purchasing information and well-defined approval processes.</p><p>For organisations planning to introduce AI into procurement, the first step should not be to automate every supplier interaction. It should be to understand how supplier information is maintained, how purchase orders are structured and how changes move through the business.</p><p>The effectiveness of supplier communication automation depends not only on how well AI understands an email, but also on how reliably the ERP system understands the business information behind it.</p><p>A well-maintained master data foundation gives Dynamics 365 the context required to support more informed procurement decisions, more consistent supplier interactions and better control over supply chain commitments.</p><p><em>Originally published at </em><a href="https://www.dynamicsmonk.com/blog/supplier-communications-agent-dynamics-365-master-data"><em>https://www.dynamicsmonk.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f3800ec3274" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Copilot vs Agents in Dynamics 365: Who Governs What, and What It Costs]]></title>
            <link>https://medium.com/@DynamicsMonkmarketing/copilot-vs-agents-in-dynamics-365-who-governs-what-and-what-it-costs-0beeea6750ff?source=rss-bb2d7dbad27f------2</link>
            <guid isPermaLink="false">https://medium.com/p/0beeea6750ff</guid>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[microsoft-copilot]]></category>
            <category><![CDATA[dynamics-365]]></category>
            <dc:creator><![CDATA[Dynamic Monk]]></dc:creator>
            <pubDate>Tue, 10 Nov 2026 06:22:51 GMT</pubDate>
            <atom:updated>2026-11-10T06:22:51.405Z</atom:updated>
            <content:encoded><![CDATA[<p>Copilot and agents often get discussed as one thing in Dynamics 365. They are not, and the difference changes how you govern and budget for them.</p><p>Copilot assists a signed-in user and works inside that user’s permissions, so security roles, field-level security and sensitivity labels do most of the governing. It is licensed per user.</p><p>Agents start from triggers or schedules, run under their own identity and are billed through Copilot Credits consumption. That means limits, testing, audit trails and a named owner, plus a budget for usage and for the people who supervise them.</p><p>If you are planning for 2026, treat them as two separate decisions. Read the full breakdown on the Dynamics Monk blog: <a href="https://www.dynamicsmonk.com/blog/copilot-vs-agents-dynamics-365-governance-cost">https://www.dynamicsmonk.com/blog/copilot-vs-agents-dynamics-365-governance-cost</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0beeea6750ff" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Business Central vs Finance and Operations: How to Choose | Dynamics Monk]]></title>
            <link>https://medium.com/@DynamicsMonkmarketing/business-central-vs-finance-and-operations-how-to-choose-dynamics-monk-f26aaf688d59?source=rss-bb2d7dbad27f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f26aaf688d59</guid>
            <dc:creator><![CDATA[Dynamic Monk]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 06:27:53 GMT</pubDate>
            <atom:updated>2026-11-09T06:27:53.827Z</atom:updated>
            <content:encoded><![CDATA[<p>A business can outgrow its spreadsheets, outgrow its accounting software, and outgrow the processes that once made it efficient. But when it starts expanding into new companies, markets or product lines, another question appears: has it outgrown its ERP, or has the business simply become more complex to manage?</p><p>For organisations evaluating Microsoft Dynamics 365, this often leads to a choice between Business Central and Finance and Operations. Both support financial and operational processes, but they are designed for different levels and types of business complexity.</p><p>Choosing the right platform is not simply a matter of employee count or annual revenue. It requires understanding how the group manages its legal entities, financial reporting, supply chain, manufacturing, integrations and future expansion.</p><p>For technical consultants, functional consultants and software engineers, the distinction matters from the beginning. The ERP choice influences implementation design, data architecture, customisation, integrations, testing and long-term maintenance.</p><h3>Business Central vs. Finance and Operations: What Is the Actual Difference?</h3><p>Microsoft Dynamics 365 Business Central is designed primarily for small and midsize organisations that need an integrated system for finance, sales, purchasing, inventory, projects and related business processes. Its capabilities can be extended through configuration, extensions and solutions available through Microsoft AppSource. The Premium licence adds enhanced service management and manufacturing capabilities. Microsoft’s Business Central overview explains its current positioning.</p><p>Finance and Operations is a commonly used name for Microsoft’s enterprise ERP applications. The current product structure separates key capabilities into Dynamics 365 Finance and Dynamics 365 Supply Chain Management, which organisations can use together depending on their requirements.</p><p>Dynamics 365 Finance focuses on financial management, financial planning, reporting, regulatory requirements and complex financial operations. Supply Chain Management supports areas such as procurement, production, inventory, warehousing, planning and logistics.</p><p>The important distinction is not that Business Central is only for small companies and Finance and Operations is only for large ones. Business Central supports multiple companies and substantial operational functionality. The enterprise applications become more relevant when the organisation’s processes, operating structure or control requirements demand their deeper capabilities.</p><h3>1. Who Is the ERP For: One Company or a Growing Group?</h3><p>The first question is how the organisation operates today and how it expects to operate in the next few years.</p><p>A company with a central finance team, a relatively straightforward operating model and a limited number of business processes may find Business Central sufficient, even as revenue and headcount grow.</p><p>A group operating through several legal entities, countries, business units or distinct operating models may have more demanding requirements. It may need consistent financial controls across entities, consolidated reporting, intercompany transactions and standardised processes without losing the ability to manage local requirements.</p><p>Both platforms support multiple-company scenarios, but the implementation approach and available capabilities differ.</p><p>Business Central can be a good fit when the group needs a practical, integrated system with a manageable level of financial and operational complexity. Finance and Supply Chain Management deserve closer evaluation when the group needs more advanced enterprise controls, broader operational coordination or complex processes across multiple entities.</p><p>The deciding question: Does the group need to manage several companies, or does it need to coordinate a complex enterprise operating model across those companies?</p><h3>2. What Does Finance Need Beyond Accounting?</h3><p>Basic accounting, payables, receivables and general ledger functionality are only part of the decision.</p><p>As a group grows, finance teams may need to manage multiple currencies, intercompany transactions, group reporting, different tax and regulatory requirements, financial planning, complex allocations and faster period-end closing.</p><p>Business Central offers integrated financial management for many growing organisations. It can support multiple companies and currencies, along with reporting and processes appropriate to its scope.</p><p>Dynamics 365 Finance becomes more relevant when financial operations require deeper enterprise capabilities, more complex financial structures and broader support for global operations. Its current feature set includes financial planning and analysis, cash-flow forecasting, subscription billing, regulatory support and capabilities intended to help finance teams manage closing activities. Microsoft’s Finance overview provides details of these capabilities.</p><p>For functional consultants, the important task is to map the actual finance processes before recommending a product. Questions about consolidation, intercompany settlements, local compliance, approval structures and financial dimensions should be answered during requirements discovery, not after configuration begins.</p><p>For developers, the same decisions affect data integration, reporting design, extensions and the way financial information is shared with other systems.</p><p>The deciding question: Can the group’s financial requirements be met through Business Central’s standard capabilities and suitable extensions, or do they call for the broader enterprise functionality of Dynamics 365 Finance?</p><h3>3. How Complex Are the Supply Chain and Manufacturing Processes?</h3><p>Operational complexity can be a stronger indicator than company size.</p><p>A distributor with straightforward purchasing, inventory and order fulfilment may operate effectively on Business Central. Its Premium plan also includes manufacturing and service management capabilities, making it relevant to organisations that need these functions without the full scope of an enterprise supply-chain platform.</p><p>The assessment changes when the business manages complex production planning, multiple warehouses, detailed manufacturing requirements, supplier coordination, advanced demand planning or a large network of operational dependencies.</p><p>Dynamics 365 Supply Chain Management is designed for more demanding supply-chain environments. Its capabilities cover planning, procurement, manufacturing, warehousing, transportation and asset management.</p><p>For example, a group with several manufacturing facilities may need to coordinate material availability, production schedules, inventory movements and supplier commitments across locations. The system must support the relationships between these processes, not simply record their transactions.</p><p>A growing business should therefore assess its current operational requirements alongside the next stage of expansion. Choosing a more extensive platform without a clear need can introduce unnecessary implementation effort. Choosing a platform that cannot adequately support the required operating model can lead to workarounds and additional systems.</p><p>The deciding question: Does the business need integrated core operations, or does it need advanced planning and coordination across a complex supply chain?</p><h3>4. What Will the ERP Cost Beyond the Licence?</h3><p>Licence pricing is important, but it does not represent the full cost of an ERP implementation.</p><p>The total cost includes implementation services, configuration, data migration, integrations, custom development, testing, training, support, ongoing maintenance and future changes. Infrastructure, additional services and licensing requirements can also affect the overall investment.</p><p>Business Central generally offers a more straightforward starting point for organisations whose requirements fit its standard functionality. Its extension ecosystem can help address specific business needs without requiring every requirement to be developed from scratch.</p><p>Finance and Supply Chain Management can support more complex enterprise scenarios, but the implementation may require more detailed process design, data governance, integration planning and specialist development.</p><p>Microsoft’s India pricing pages provide a useful starting point for comparison. At the time of research, Business Central Essentials was listed at ₹6,655 per user per month and Premium at ₹9,150, while Dynamics 365 Finance and Supply Chain Management were each listed at ₹17,470 per user per month for their standard plans. Prices are indicative, billed yearly, with GST extra where applicable; actual costs depend on licensing requirements and may change.</p><p>These figures should not be treated as a direct total-cost comparison. The products have different capabilities, licensing models and implementation requirements. Organisations should validate the required user licences, attach licences, add-ons, capacity and service costs before preparing a business case.</p><p>The deciding question: Which platform delivers the required capabilities at an acceptable total cost over the expected life of the solution?</p><h3>5. How Much Customisation and Integration Will Be Required?</h3><p>An ERP rarely operates in isolation. It may need to connect with CRM applications, e-commerce platforms, warehouse systems, banking services, reporting tools, external applications and custom business software.</p><p>Business Central supports integrations and extensions through its platform and partner ecosystem. Its AL development model allows developers to extend application functionality while keeping custom code separate from the standard application.</p><p>Finance and Operations applications have their own extensibility model, development tooling and integration patterns. Microsoft’s supported approach relies on extensions rather than overlayering the standard application code. This is important because customisations must remain maintainable as Microsoft delivers application updates. Microsoft Learn’s extensibility guidance explains the approach for Finance, Supply Chain and Commerce.</p><p>For technical teams, the assessment should include more than whether an integration is technically possible. They need to understand data ownership, transaction volumes, error handling, security, monitoring and the effort required to maintain the integration.</p><p>The team should also distinguish between a genuine product gap and a requirement that can be met through configuration, an existing extension or a supported integration. Unnecessary customisation increases complexity and can make future upgrades more difficult.</p><p>The deciding question: Can the required architecture be delivered through standard capabilities and supported extensions, or does the operating model need the broader enterprise platform?</p><h3>6. What Has Changed in Microsoft’s ERP Roadmap?</h3><p>Product selection should account for the direction in which Microsoft is investing, not just the functionality available today.</p><p>Microsoft’s 2026 release wave 1 introduced or planned improvements across both product families. For Business Central, the focus included AI-assisted business processes, expanded agent capabilities, developer productivity and improvements across finance, manufacturing and supply-chain operations. Microsoft Learn’s Business Central release overview describes the release wave covering April to September 2026.</p><p>For Dynamics 365 Finance, Microsoft’s 2026 investments included financial automation, multi-entity capabilities, improvements to financial planning and analytics, and support for additional business models such as rentals. Supply Chain Management updates included enhancements to demand planning, supplier communication and warehouse operations. Microsoft’s Finance release overview and Supply Chain Management release overview provide further detail.</p><p>Another relevant change concerns how Microsoft publishes product updates. Since September 2026, Microsoft has moved away from publishing new Dynamics 365 and Power Platform release plans twice a year. New capabilities are being published through its AI at Work roadmap, while existing release plans remain available as historical references. Teams assessing an ERP should therefore review the current roadmap and product documentation rather than treating an older release plan as a complete picture of future functionality. Microsoft’s release-plan guidance explains the change.</p><p>AI features are worth evaluating, but they should not determine the ERP choice on their own. Teams should assess the business process an AI capability supports, its availability, licensing requirements, data access and governance before including it in an implementation plan.</p><h3>7. How Should Consultants Make the Final Decision?</h3><p>A structured assessment is more useful than choosing a product based on a single measure such as revenue, user count or the number of legal entities.</p><p>Start by documenting the group’s operating model, financial requirements, supply-chain processes, reporting obligations and integration landscape. Separate current requirements from planned expansion, then identify which requirements each platform can support through standard functionality, configuration or extensions.</p><p>Next, assess the implementation implications. Functional consultants should validate business processes and identify gaps. Technical consultants should evaluate architecture and integration needs. Developers should assess extensibility, data movement and long-term maintainability. Finance and business stakeholders should compare total cost, implementation risk and expected benefits.</p><p>Finally, validate any critical requirements through demonstrations or a proof of concept. A product may appear suitable at a high level but expose important limitations when tested against the organisation’s actual processes.</p><p>The recommendation should explain not only which ERP fits best, but also why the alternative is less suitable for the group’s needs.</p><h3>Choose for the Complexity You Need to Manage</h3><p>Business Central and Dynamics 365 Finance and Supply Chain Management serve different business requirements within Microsoft’s ERP portfolio. Neither should be selected simply because a company has reached a particular revenue level or number of employees.</p><p>Business Central is a strong candidate for growing organisations that need integrated finance and operations with a focused implementation scope. Finance and Supply Chain Management warrant consideration when financial structures, operational processes, global requirements or supply-chain demands call for deeper enterprise capabilities.</p><p>For Dynamics Monk, the assessment should begin with the business model, not the product name. Understand how the group operates, identify where complexity is increasing, map the requirements to Microsoft’s capabilities and evaluate the long-term cost of each option.</p><p>The right ERP is the one that supports the group’s next stage of growth without adding complexity the business does not need.</p><p><em>Originally published at </em><a href="https://www.dynamicsmonk.com/blog/business-central-vs-finance-and-operations"><em>https://www.dynamicsmonk.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f26aaf688d59" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dataverse Capacity After Go-Live: Database, File and Log Growth | Dynamics Monk]]></title>
            <link>https://medium.com/@DynamicsMonkmarketing/dataverse-capacity-after-go-live-database-file-and-log-growth-dynamics-monk-9e6396eb761c?source=rss-bb2d7dbad27f------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e6396eb761c</guid>
            <dc:creator><![CDATA[Dynamic Monk]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 06:26:55 GMT</pubDate>
            <atom:updated>2026-11-09T06:26:55.255Z</atom:updated>
            <content:encoded><![CDATA[<p>A Microsoft Dataverse environment may operate within its allocated storage limits during implementation and still face capacity pressure several months after go-live. As users create records, upload documents, run workflows and interact with business applications, storage consumption continues to grow.</p><p>This growth is not always visible to finance teams until a capacity report shows limited remaining storage or additional capacity needs to be purchased.</p><p>The challenge is that Dataverse does not use a single storage category. It separates consumption into database, file and log capacity. Each category serves a different purpose, and each grows according to different usage patterns.</p><p>Understanding these differences is essential for organisations using Microsoft Power Platform and Dynamics 365. Effective Dataverse capacity planning helps administrators identify the source of storage growth, forecast future requirements and manage costs before capacity becomes an operational concern.</p><h3>What Is Dataverse Capacity Planning?</h3><p>Dataverse capacity planning is the process of monitoring current storage consumption, understanding what drives growth and estimating the capacity required to support future business activity.</p><p>It involves more than checking the total storage available in an environment. Administrators must understand how records, documents, images, auditing and system-generated data contribute to different storage categories.</p><p>For example, a customer service application may generate database growth through case records and related activities. The same application may consume file capacity through email attachments and uploaded documents. If auditing is enabled, changes to records can also contribute to log capacity.</p><p>These activities may occur within the same application, but their storage impact is not identical.</p><p>A practical Dataverse capacity planning strategy therefore begins with understanding the three storage categories.</p><h3>Understanding the Three Dataverse Storage Categories</h3><h3>1. Database Capacity: Structured Business Data</h3><p>Database capacity supports the structured data stored in Dataverse. This includes business records, relationships between tables and other database components required by applications.</p><p>Common contributors include:</p><ul><li>Account, contact, lead and case records</li><li>Custom tables and their associated records</li><li>Activities and other transactional data</li><li>System and application metadata that contributes to database consumption</li><li>Database indexes and related storage overhead</li></ul><p>Database consumption often increases as organisations expand their use of Dynamics 365 and Power Platform applications. New business units, additional processes, higher transaction volumes and custom tables can all contribute to growth.</p><p>For example, an organisation that initially uses Dynamics 365 for sales may later introduce customer service processes, additional custom tables and integrations with external systems. As the volume of records increases, database consumption may rise accordingly.</p><p>What finance teams should understand: Database growth is closely connected to business activity and application design. Forecasting should account for expected record volumes, new workloads and changes to data retention practices.</p><h3>2. File Capacity: Documents, Attachments and Images</h3><p>File capacity supports files stored within Dataverse. This can include documents attached to business records, images, email attachments and content stored in supported file columns.</p><p>Common contributors include:</p><ul><li>Email attachments</li><li>Notes and documents attached to records</li><li>Images uploaded through business applications</li><li>Files stored in Dataverse file columns</li><li>Other supported file-based content</li></ul><p>File consumption can increase rapidly when applications become part of everyday document-handling processes.</p><p>Consider a customer service team that stores invoices, screenshots, signed forms and supporting documents against customer cases. Each file may appear small in isolation, but thousands of cases can create substantial storage demand over time.</p><p>The same pattern can occur in field service, healthcare, financial services and other environments where users regularly upload supporting documents.</p><p>What finance teams should understand: File capacity should be forecast separately from database capacity. An organisation may have a manageable volume of structured records while storing a growing collection of large attachments and documents.</p><h3>3. Log Capacity: Auditing and System Activity</h3><p>Log capacity supports specific types of system-generated data. Depending on the features and workloads in use, this can include audit history, plug-in trace logs and applicable elastic-table data.</p><p>Common contributors include:</p><ul><li>Dataverse auditing records</li><li>Plug-in trace logs</li><li>Other supported log data generated by application activity</li></ul><p>Auditing is particularly important to understand. When auditing is enabled, Dataverse can record changes to data and other configured activities. This information helps organisations investigate changes, support compliance requirements and maintain accountability.</p><p>However, retaining audit history also has a storage cost. The volume generated depends on the tables and activities being audited, transaction frequency and retention settings.</p><p>Plug-in trace logging can also contribute to consumption, especially when detailed logging remains enabled for troubleshooting over extended periods.</p><p>What finance teams should understand: Log growth is influenced by configuration and operational practices, not only by the number of business records. Retention requirements and logging settings should be reviewed alongside storage forecasts.</p><h3>Why Dataverse Capacity Changes After Go-Live</h3><p>Storage consumption rarely remains static after implementation. Once users begin working in the environment, real operational patterns replace the assumptions made during project planning.</p><p>Several factors can influence Dataverse capacity growth.</p><h3>Increasing Transaction Volumes</h3><p>As more employees use Dynamics 365 and Power Platform applications, the number of records and related activities increases. New teams, business units and workflows can accelerate this growth.</p><h3>Expanding Document Usage</h3><p>Users may begin attaching more documents to records than originally anticipated. Email integrations, image uploads and file-based processes can increase file consumption even when database growth remains relatively stable.</p><h3>Auditing and Troubleshooting</h3><p>Audit history and plug-in trace logs can accumulate as systems process more transactions. Without suitable retention and cleanup practices, older data may continue to consume storage.</p><h3>Integrations and Automation</h3><p>Integrations can create additional records, update existing information and generate supporting activity data. Automated processes may run frequently and produce more data than manual workflows.</p><h3>Changes to Application Scope</h3><p>A Dataverse environment that initially supports one application may eventually serve several departments or business processes. Additional tables, records, documents and automation can change its storage profile significantly.</p><p>These factors make post-go-live monitoring essential. Initial capacity estimates should be treated as a baseline that requires regular review, rather than a permanent measure of future requirements.</p><h3>How Dataverse Capacity Entitlements Work</h3><p>Microsoft Dataverse capacity is managed through separate database, file and log categories. The available capacity depends on the organisation’s licences, applicable entitlements and any additional storage purchased.</p><p>Organisations should review their actual entitlements in the Power Platform admin center rather than relying on assumptions based on the number of users alone.</p><p>Capacity categories also have specific rules governing how excess consumption is handled. Where Microsoft’s applicable capacity-borrowing rules permit it, unused capacity in one category may help offset an overage in another. The direction and limits of this borrowing must be checked against the current Microsoft documentation and the organisation’s entitlement.</p><p>This distinction matters because unused capacity in one category does not automatically mean every other category has sufficient storage.</p><p>For example, an organisation might have available database capacity but still exceed its file allocation because of document-heavy workloads. Administrators should evaluate each category individually and verify whether any applicable borrowing rules reduce the effective overage.</p><h3>What Happens When Dataverse Exceeds Its Capacity?</h3><p>When an organisation exceeds its available Dataverse storage, it may need to reduce consumption, acquire additional capacity or both. The impact depends on the category involved and the applicable Microsoft enforcement rules.</p><p>Capacity pressure can create several challenges:</p><ul><li>Additional costs: The organisation may need to purchase extra storage to support continued usage.</li><li>Operational constraints: Certain administrative or environment operations may be restricted under applicable over-capacity rules.</li><li>Unplanned budget requirements: Finance teams may have to accommodate storage costs that were not included in the original project budget.</li><li>Reduced planning visibility: Without reliable forecasts, it becomes harder to distinguish temporary growth from a sustained increase in storage requirements.</li></ul><p>The exact consequences depend on Microsoft’s current policies, licensing arrangements and the environment’s status. Administrators should consult the Power Platform admin center and current Microsoft documentation before deciding on remediation.</p><h3>How to Monitor Dataverse Capacity</h3><p>The Power Platform admin center is the primary place to review Dataverse capacity consumption and available storage information.</p><p>Administrators should examine database, file and log usage separately, identify environments with high consumption and compare current usage with previous reports where historical data is available.</p><p>Monitoring should focus on both the current position and the rate of change.</p><p>For example, an environment using 80% of its database allocation may appear manageable. However, if consumption has increased significantly over the previous few months, the organisation may need to act sooner than an environment with higher usage but slower growth.</p><p>A useful monitoring approach includes:</p><ul><li>Reviewing storage consumption by category</li><li>Identifying environments approaching their available capacity</li><li>Investigating the tables and activities contributing to growth</li><li>Reviewing file-heavy processes and retention practices</li><li>Monitoring auditing and plug-in trace logging</li><li>Comparing actual consumption with projected business growth</li></ul><p>Administrators should also account for reporting delays. Storage figures may not immediately reflect cleanup or deletion activities, so changes should be validated through subsequent reports rather than assumed to appear instantly.</p><h3>Managing Dataverse Storage Growth</h3><p>Capacity management is most effective when it combines technical investigation with clear data-retention policies.</p><h3>Review Data Retention</h3><p>Identify records and logs that are no longer required for business operations, compliance or reporting. Apply retention rules that reflect the organisation’s obligations before removing historical data.</p><h3>Investigate File Consumption</h3><p>Review document-heavy processes, including email attachments, images and files associated with business records. Establish suitable practices for managing older files where retention requirements allow.</p><h3>Manage Auditing and Trace Logs</h3><p>Confirm that auditing is enabled for the tables and activities that require it. Review retention settings and troubleshooting practices to avoid retaining unnecessary log data indefinitely.</p><h3>Assess Application and Integration Design</h3><p>Review custom tables, integrations and automated processes that create or duplicate records. Where appropriate, refine the design to reduce unnecessary data generation while preserving business requirements.</p><h3>Plan Additional Capacity Where Necessary</h3><p>Cleanup alone may not be sufficient when storage growth reflects legitimate business demand. If the organisation expects continued expansion, additional capacity may be the appropriate option.</p><p>The objective is not simply to reduce storage consumption. It is to ensure that the organisation retains the data it needs while keeping capacity costs predictable.</p><h3>Forecasting Dataverse Capacity for Finance Teams</h3><p>Finance teams need a forecast that connects storage consumption with business activity and expected costs.</p><p>A practical starting point is to estimate the current usage, monthly growth rate and expected change in workload for each storage category.</p><p>For example, if database consumption is increasing by 5 GB per month, the organisation can use that trend as an initial estimate of future requirements. The forecast should then be adjusted for planned projects, new integrations, changing transaction volumes and expected data-retention activities.</p><p>The calculation is straightforward:</p><p>Projected capacity requirement = Current consumption + Expected growth over the forecast period</p><p>Suppose an environment currently uses 80 GB of database capacity and is expected to grow by 5 GB per month. At the same growth rate, projected consumption after six months would be approximately 110 GB, before accounting for any changes in workload or cleanup.</p><p>This estimate is not a substitute for detailed capacity analysis, but it provides a starting point for budget discussions.</p><p>Finance and IT teams should review forecasts together. IT can explain the technical drivers of storage growth, while finance can assess the likely cost implications and timing of additional capacity requirements.</p><h3>Dataverse Capacity Planning Must Continue After Go-Live</h3><p>Dataverse capacity planning is an ongoing operational responsibility, not a one-time implementation task. Database, file and log consumption respond to different patterns of business activity, application design and data-retention practices.</p><p>Organisations that monitor these categories separately can identify growth earlier, make better-informed licensing decisions and reduce the risk of unexpected storage costs.</p><p>For finance and IT teams, the goal is straightforward: understand what is consuming capacity, estimate how demand will change and make storage decisions before the environment reaches its limits.</p><p><em>Originally published at </em><a href="https://www.dynamicsmonk.com/blog/dataverse-capacity-planning-after-go-live"><em>https://www.dynamicsmonk.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e6396eb761c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Copilot vs Agents in Dynamics 365: Governance and Cost | Dynamics Monk]]></title>
            <link>https://medium.com/@DynamicsMonkmarketing/copilot-vs-agents-in-dynamics-365-governance-and-cost-dynamics-monk-4c500992881a?source=rss-bb2d7dbad27f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c500992881a</guid>
            <dc:creator><![CDATA[Dynamic Monk]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 06:25:36 GMT</pubDate>
            <atom:updated>2026-11-09T06:25:36.395Z</atom:updated>
            <content:encoded><![CDATA[<p>A seller asks Copilot to summarise an account before a call. Overnight, a research agent updates forty opportunities on its own. Both run inside Dynamics 365, but they carry very different risks and costs. Here is where the boundary sits, which controls apply on each side, and what you should budget.</p><p>Quick answer: Copilot assists a person inside that person’s permissions and is licensed per user. Agents act under their own identity and are billed by consumption. Govern Copilot through data permissions. Govern agents through identity, limits, testing and audit.</p><h3>Where the Boundary Sits</h3><p>The simplest test is who starts the work and who checks the result. Copilot waits for a prompt and a person reviews the output. An agent can start from a trigger, a schedule or another agent, and may write records without review.</p><ul><li>Starts when: Copilot — a user prompts it | Agents — a trigger, schedule or another agent</li><li>Runs as: Copilot — the signed-in user | Agents — its own identity, or a stored connection</li><li>Billing: Copilot — per-user licence | Agents — Copilot Credits (consumption)</li><li>Main risk: Copilot — surfacing data users should not see | Agents — wrong actions at scale, runaway cost</li><li>Main control: Copilot — security roles | Agents — identity, limits, testing, audit</li></ul><h3>Why the Line Is Blurring in 2026</h3><p>Two Dynamics 365 Sales agents reached general availability in April 2026: the Opportunity Research Agent on 15 April and the Sales Research Agent on 30 April. Copilot Studio now supports multi-agent orchestration, so several agents can work together as one coordinated system.</p><p>Connectivity has widened too. An MCP server lets a single agent pull context from Business Central, Dataverse and SharePoint in one conversation. MCP (Model Context Protocol) is an open standard that lets an agent call tools and read data in other systems. One agent can now touch several systems in a single task, so your governance must follow the whole chain.</p><h3>Governing Copilot: The Data Layer</h3><p>Copilot has no powers of its own. It reads what the user can read. That makes the controls familiar:</p><ul><li>Security roles and business units in Dataverse. Review privilege depth (user, business unit, organisation). Broad “organisation” read access is the usual cause of oversharing.</li><li>Field-level security. Protect columns such as pricing, margin or personal data, so they stay hidden even if the table is readable.</li><li>Sensitivity labels and Purview policies. These keep Microsoft 365 content, which Copilot also draws on, correctly classified.</li><li>Licence mapping. Copilot in Microsoft 365 and Copilot inside a Dynamics 365 app are different products. One licensing advisory warns that users needing both can face about $60 per user per month in AI spend on top of base licences. Verify your own agreement.</li></ul><h3>Governing Agents: Five Technical Controls</h3><p>1. Identity. Every agent needs its own identity, not a shared login. With Agent 365, every agent receives its own Agent ID, so least-privilege permissions can be applied to each one. Conditional Access for agents requires Entra ID P1 or P2, and access reviews and lifecycle workflows require Entra ID Governance.</p><p>2. Connection model. Decide whether the agent runs as the end user or under a fixed account. A fixed account with broad rights quietly lets every user reach data they should not. Prefer user-based authentication for anything that reads sensitive records.</p><p>3. Environments and connector policy. Keep development, test and production in separate Power Platform environments. Use data loss prevention (DLP) policies to classify connectors as business, non-business or blocked, so an agent cannot move CRM data into a consumer service. Managed Environments add usage reporting and sharing limits.</p><p>4. Limits and monitoring. Set caps before launch. Dynamics 365 AI Hub in Customer Insights — Journeys lets admins set guardrails such as follow-up limits and processing caps, and monitor usage per environment. Log agent activity in Purview audit so you can show what an agent did and why.</p><p>5. Testing and input safety. Agents that read emails, documents or web content can be manipulated by hidden instructions, known as prompt injection. At RSAC 2026, Microsoft added network-level prompt-injection blocking through Entra Internet Access. Test agents against hostile inputs, and add a human approval step before any write action that cannot be undone.</p><h3>What Each Side Costs</h3><p>Copilot is predictable: per-user licences, plus the time to tidy permissions and train staff.</p><p>Agents have four cost layers:</p><ul><li>Consumption. Agents use Copilot Credits when they interact with users or act on a user’s behalf. Pay-as-you-go costs $0.01 per credit, and a prepaid pack of 25,000 credits costs $200 per month. Microsoft moved from per-message to per-credit billing in September 2025. As an illustration, an agent consuming 100,000 credits a month costs about $1,000.</li><li>Bundled allowances. Dynamics 365 Sales Premium includes 1,000 Copilot Credits per user each month, and credits are required to run prebuilt and custom agents. Employee-facing agents used by people with a Microsoft 365 Copilot licence are included at no extra credit cost, within fair usage limits.</li><li>Control tooling. Agent 365 became generally available on 1 May 2026, licensed per user. The price is $15 per user per month. Microsoft says it works best with Microsoft E5 as a base.</li><li>People time. Owners, reviews, testing and retirement. This is usually the largest cost and rarely appears in a quote.</li></ul><p>Billing is also configured per environment. Pay-as-you-go is set through a billing plan linked to each environment. Map each agent to the environment, and the cost centre, that will carry its bill.</p><h3>A Five-Check Test Before Handing Work to an Agent</h3><ul><li>Reversibility: can the action be undone?</li><li>Sensitivity: does it touch personal, financial or contract data?</li><li>Volume: will it run hundreds of times a day?</li><li>Ownership: is a named person accountable?</li><li>Evidence: can you show an auditor the full trail?</li></ul><p>Fail two or more, and keep a person in the loop.</p><h3>Frequently Asked Questions</h3><h3>Does Microsoft 365 Copilot cover agent usage in Dynamics 365?</h3><p>Only partly. Zero-rating applies to employee-facing agents for licensed users. Autonomous agents and Dynamics 365 agents can still consume credits, so check each agent’s billing.</p><h3>Do we need Agent 365 to use agents?</h3><p>No. It is a control layer, not a requirement. Once agents multiply across teams, a central registry and agent identities become hard to do without.</p><h3>Can an agent see more data than the user who triggered it?</h3><p>Yes, if it runs under a fixed account with wide permissions. This is why the connection model matters.</p><h3>Final Thoughts</h3><p>Copilot helps a person act, so its governance centres on data permissions. Agents act themselves, so governance extends to identity, limits, testing and audit, plus a consumption bill that grows with use. Budget for supervision from day one.</p><p><em>Originally published at </em><a href="https://www.dynamicsmonk.com/blog/copilot-vs-agents-dynamics-365-governance-cost"><em>https://www.dynamicsmonk.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c500992881a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[No Release Wave 2 This Year? How to Build a Dynamics 365 Change Calendar]]></title>
            <link>https://medium.com/@DynamicsMonkmarketing/no-release-wave-2-this-year-how-to-build-a-dynamics-365-change-calendar-8b49d4ab4f53?source=rss-bb2d7dbad27f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b49d4ab4f53</guid>
            <dc:creator><![CDATA[Dynamic Monk]]></dc:creator>
            <pubDate>Fri, 30 Oct 2026 07:49:05 GMT</pubDate>
            <atom:updated>2026-10-30T07:49:05.330Z</atom:updated>
            <content:encoded><![CDATA[<p>For years, Dynamics 365 teams opened the same calendar entry each October: review release wave 2. This year there is no wave 2 for 2026 and no release plan document to read. That does not mean updates have stopped. Microsoft now ships new features on a single roadmap, so the warning system is different, not the pace of change.</p><p>The fix is a change calendar of your own. Name one owner for the roadmap, set a fixed monthly review, and sort every change into act now, plan or watch. Match each change to a testing window, then add communication and training dates so users are never surprised by a new button.</p><p>The full guide covers a five-step setup, a four-week calendar template and the common mistakes to avoid. Read it here: <a href="https://www.dynamicsmonk.com/blog/dynamics-365-change-calendar-no-release-wave">https://www.dynamicsmonk.com/blog/dynamics-365-change-calendar-no-release-wave</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b49d4ab4f53" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is There a Dynamics 365 Release Wave 2 in 2026? What to Do Next]]></title>
            <link>https://medium.com/@DynamicsMonkmarketing/is-there-a-dynamics-365-release-wave-2-in-2026-what-to-do-next-292aec430be2?source=rss-bb2d7dbad27f------2</link>
            <guid isPermaLink="false">https://medium.com/p/292aec430be2</guid>
            <category><![CDATA[dynamics-365]]></category>
            <category><![CDATA[microsoft-dynamics-crm]]></category>
            <category><![CDATA[change-management]]></category>
            <dc:creator><![CDATA[Dynamic Monk]]></dc:creator>
            <pubDate>Thu, 29 Oct 2026 05:11:52 GMT</pubDate>
            <atom:updated>2026-10-29T05:11:52.589Z</atom:updated>
            <content:encoded><![CDATA[<p>Every October, Dynamics 365 teams used to open the same calendar entry: “Review release wave 2.” This year, that entry has nothing behind it. There is no Dynamics 365 release wave 2 for 2026, no release plan document, and no neat list of features to read through over a cup of tea.</p><p>That does not mean updates have stopped. It means the way you hear about them has changed. If your business runs on Dynamics 365, the safest response is to build your own Dynamics 365 change calendar: a shared schedule that shows what is coming, who checks it, and when it reaches your users.</p><p>This guide shows you how.</p><h3>What Microsoft Changed</h3><p>For years, Microsoft delivered updates in two release waves. Wave 1 ran from April to September. Wave 2 ran from October to March. A release plan arrived a few weeks ahead of each wave, so admins could read it, test in a sandbox, and brief their teams.</p><p>In August 2026, Microsoft announced the end of that model for Dynamics 365, Power Platform and Dataverse. New features now appear on a single roadmap, called the AI at Work roadmap, once Microsoft commits to them. The older Release Planner site is due to retire by 15 November 2026.</p><p>In short, updates now arrive as a steady stream instead of two big announcements a year. The software is not changing less. The warning system is simply different.</p><h3>Why This Matters for Your Business</h3><p>The old release plan did one useful thing: it forced a conversation. Twice a year, someone had to read the changes and decide what mattered. Without that rhythm, three risks appear.</p><p><strong>Missed changes.</strong> A new setting or a change in default behaviour can slip in unnoticed, then show up as a complaint from a user.</p><p><strong>Surprise clashes.</strong> Custom workflows, integrations and reports can break when a feature changes underneath them. A small update can cause a big problem if nobody tested it.</p><p><strong>Unplanned training.</strong> Staff find new buttons before anyone has explained them, and confidence in the system drops.</p><p>Companies that treat the roadmap as a news feed will struggle. Companies that treat it as an input to their own schedule will stay calm.</p><h3>How to Build Your Own Dynamics 365 Change Calendar</h3><p>A change calendar is a simple shared schedule. It lists every update that could affect your system, who reviews it, and when it reaches users. Here is a five-step way to build one.</p><h3>Step 1: Pick an owner</h3><p>Name one person responsible for watching Microsoft’s roadmap. This could be a functional consultant, a system admin or a technology partner. Without a named owner, the calendar becomes everyone’s job, and so nobody’s job.</p><h3>Step 2: Set a fixed review rhythm</h3><p>Replace the old wave review with a regular check. A monthly review works well for most mid-sized teams. Large organisations with many connected systems may prefer every two weeks. Block the time in advance, the same way you once blocked time for release wave 2.</p><h3>Step 3: Sort every change into three groups</h3><p>For each item on the roadmap, ask one question: what does this do to us?</p><ul><li><strong>Act now:</strong> it affects live processes, security or compliance.</li><li><strong>Plan:</strong> it is useful, but needs testing or training first.</li><li><strong>Watch:</strong> it is interesting, but no action is needed yet.</li></ul><p>This keeps your list short and your meetings useful.</p><h3>Step 4: Match each change to a testing window</h3><p>Choose a test environment and a fixed slot for checking changes before they reach your live system. Test your most important processes every time, such as quotes, orders, invoices, approvals and any link to other tools. Write down what you tested and what you found.</p><h3>Step 5: Add communication and training dates</h3><p>Every change that affects users needs a short note and, where needed, a quick training session. Put these dates on the calendar next to the technical dates. A new feature only helps if people know it exists and trust it.</p><h3>A Four-Week Dynamics 365 Change Calendar Template</h3><p>If you want a starting point, try this four-week loop.</p><ul><li><strong>Week 1:</strong> Review the roadmap and sort new items into act now, plan and watch.</li><li><strong>Week 2:</strong> Test priority items in your test environment and check connected systems.</li><li><strong>Week 3:</strong> Brief business users and update your guides.</li><li><strong>Week 4:</strong> Approve changes for release, then look back at what went well and what did not.</li></ul><p>Adjust it to your own size and pace. What matters is that the rhythm repeats, so updates become routine instead of a surprise.</p><h3>Mistakes to Avoid</h3><ul><li><strong>Waiting for a big announcement.</strong> There will not be one. Features will appear one by one, and dates can move.</li><li><strong>Treating every item as urgent.</strong> Most roadmap items will not touch your business this quarter. Sorting is the real skill.</li><li><strong>Leaving business teams out.</strong> Finance, sales and operations know which processes are fragile. Invite them to the monthly review.</li><li><strong>Skipping the record.</strong> Keep a short log of what changed, when, and who approved it. It helps with audits and speeds up fixes when something goes wrong.</li><li><strong>Trusting old dates.</strong> Roadmap timing can shift. Recheck dates at each review and update the calendar.</li></ul><h3>What This Means for Dynamics 365 Teams</h3><p>The end of release waves is a good moment to move from reacting to planning. Teams with a clear Dynamics 365 change calendar spend less time on surprises and more time using new features well.</p><p>Teams without one will feel every update as a small emergency.</p><p>At Dynamics Monk, we help organisations across the UK, UAE, Australia, Singapore and Southeast Asia keep their Dynamics 365 systems steady as Microsoft’s update model changes. Whether you need a ready-made change calendar, a testing routine, or ongoing support from certified consultants, we can set it up with you.</p><p><em>Originally published on Dynamics Monk: </em><a href="https://www.dynamicsmonk.com/blog/dynamics-365-change-calendar-no-release-wave"><em>Is There a Dynamics 365 Release Wave 2 in 2026? What to Do Next</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=292aec430be2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>