Global Inventory Accounting Ends Support on 1 July 2027: What to Inventory Now

Global Inventory Accounting is deprecated in the Dynamics 365 Supply Chain Management 10.0.49 removed-and-deprecated list. It is not removed in this update. Microsoft's status line is specific: deprecated, and end of support on 1 July 2027. The product areas are Finance and Supply Chain Management. The deployment options are cloud and on-premises.

The September self-update and the October auto-update will not rip GIA out of a production company. They do start a date you can put on a program plan. Ten months is enough to discover which legal entity actually posts through it. It is not enough if the first inventory happens in June 2027.

Microsoft's stated reason is architectural. GIA is being retired so a modernized inventory costing capability can replace it. The replacement named in the deprecation notice is a multi-ledger costing solution, described as providing comparable capabilities and significant improvements. The notice points to Microsoft's "See what's next in financial operations" post for that successor. It does not say the successor is installed and defaulted by 10.0.49. Plan a transition to supported costing. Do not plan on a silent in-place swap during the October auto-update.

Microsoft's three cases

The deprecation article tells you which action matches which footprint:

• GIA is not used in production. No action.
• GIA was only installed or enabled in a sandbox. If nobody is testing on it, disable or remove it, and stop new designs that assume it.
• Production uses it, or something depends on it. Assess usage and dependencies, plan the move to supported costing, and validate the change in a test environment before July 2027. Microsoft recommends engaging them or your implementation partner for that planning.

The second case is where side projects go to die. A sandbox enabled GIA for a costing prototype two years ago, the prototype became a customization, and production was "going to be next." That customization is now aimed at a feature with an end-of-support date. Find it while the sandbox still has the feature.

What to list before anyone debates a design

A transition plan that starts from a slide will miss the company that posts one item model through GIA and everything else through standard costing. Pull the footprint from the environment:

Question	Why it changes the plan
Which legal entities have GIA enabled in production?	Scope is a company list, not a slogan
Which item model groups or inventory relationships post through it?	One company can be mixed
Which financial statements, inventory value reports, and management reporter designs read those balances?	The successor has to land on the same statement lines
Which dual-write maps, data entities, or exports assume GIA fields?	Integrations fail after a costing change even when the UI looks fine
Which customizations reference GIA classes or tables?	Those are compile and behavior work, separate from the costing design
Is the same feature enabled only in a sandbox that was refreshed from production?	A refresh can make a sandbox look like production. Check the date of the refresh before you trust it

Write the answers down in the upgrade ticket for 10.0.49 even though the feature still works on that build. The people who know why GIA was enabled are not always the people who will own July 2027.

What this deprecation does not decide

Multi-ledger costing is the named direction. The 10.0.49 feature tables do not list it as a switch you turn on next to GIA. Until Microsoft publishes the configuration, the data migration, and the statement mapping for that solution, the responsible step is the inventory above plus a test environment where you can post the same receipt, adjustment, and production issue under the costing method you intend to keep.

Do not disable GIA in production to "get ahead of the deprecation." End of support is not a removal in this release. Disabling it changes inventory accounting now. The deprecation notice says to validate in a test environment first, and that instruction is the whole point.

Companies that never enabled GIA should spend their 10.0.49 time on the mandatory quality, bank, and settlement changes instead. Those change behavior in October. GIA does not, until you touch it.

The other removal in the same 10.0.49 list

The same deprecated-features article removes follow-up questions in the Copilot sidecar. Microsoft discontinued the preview. It never reached general availability, and it is gone from finance and operations apps, cloud and on-premises. There is no replacement named. Demo scripts and test cases that asked a second question in that sidecar will fail after the update. That is a deleted preview, not a costing migration. Mention it in the upgrade notes so someone does not file it as a regression against Copilot in the client.

The costing date and the sidecar removal are independent. Only one of them needs a program. If production uses GIA, name an owner this month, book a test environment, and put 1 July 2027 on the plan as the date support ends — not as the date you intend to start looking.