Microsoft folds sustainability into Dynamics 365: what NZ firms gain

What Microsoft announced

On 3 November, Microsoft announced that Microsoft Sustainability Manager is joining the Dynamics 365 ERP portfolio under the name Dynamics 365 Sustainability. The announcement came in a post by April Olson, Microsoft's chief product officer for Dynamics 365 Finance, Human Resources and Sustainability. The product records carbon, water and waste data, calculates Scope 1, 2 and 3 emissions, and prepares disclosures against frameworks including CSRD, GRI, SASB and the IFRS Sustainability Disclosure Standards.

Olson's post lists the planned work. The calculation side gets enhanced data trails, calculation versioning and reporting-period controls. Partner emissions and product carbon footprint data will feed into Scope 3 calculations. Microsoft is adding Dataverse MCP server support so agents can work with sustainability data, and it plans a "green ledger view" that puts financial and emissions figures side by side, along with closer interoperability with Dynamics 365 Finance. The post gives no release dates for any of these items, and ERP Today reports that the Copilot features on the product page are still labelled preview.

What changes now, and what stays the same

Directions on Microsoft analyst Andrew Snodgrass called the change a new name for the same product. His report says tiers, features and costs carry over unchanged, and existing customers shouldn't expect immediate differences beyond the branding. MSDynamicsWorld puts the Essentials tier at US$4,000 per tenant per month and Premium at US$12,000, and says those prices appear to be staying. Directions adds that the full bill still depends on Dataverse storage, AI features billed by consumption, and the external supplier portal used to gather ESG data.

The practical news for buyers is about where Microsoft now sells emissions accounting. Microsoft is placing it next to the general ledger and procurement data, and the same ERP sales teams and partners will sell it. For finance directors, the green ledger is the part to watch: it points towards emissions figures that trace back to the same transactions behind the financial statements, and auditors and boards have been asking for that link. Microsoft hasn't published how the green ledger will work or when it'll ship, so any budget built around it rests on assumptions.

Why NZ and Australian firms should pay attention

New Zealand's mandatory climate reporting regime covers a fairly small group. The Ministry for the Environment says about 200 entities report, mainly large banks, insurers, investment scheme managers and listed issuers above a $60 million threshold. In October 2025 the Government announced plans to raise the listed-issuer threshold to $1 billion and take managed investment schemes out of the regime. Bell Gully's summary says the changes would go through the Financial Markets Conduct Amendment Bill, with passage expected in 2026.

Australia's regime keeps growing. Group 2 entities began their first mandatory reporting period on 1 July 2026. Group 2 includes companies meeting at least two of these tests: consolidated revenue above $200 million, gross assets above $500 million, or more than 250 employees, according to Watershed's guide.

For most NZ businesses, supplier requests will matter more than direct obligations. Scope 3 counts the emissions in a reporter's value chain, and Olson's post says partner emissions data will now feed Scope 3 calculations in Microsoft's product. Large Australian and NZ reporters need emissions figures from the companies they buy from, and plenty of NZ manufacturers, food producers, freight operators and wholesalers sell to those reporters. Those suppliers will get asked for emissions per product or per shipment, even though no law requires them to publish a climate statement themselves.

What the move means for your ERP

Most NZ mid-market Microsoft customers run Business Central. Microsoft's announcement names Dynamics 365 Finance as the integration target, and neither Olson's post nor ERP Today's coverage describes features aimed at Business Central. At US$4,000 a month for the entry tier, Dynamics 365 Sustainability suits large reporting entities with many sites and complex Scope 3 calculations. A supplier that answers a few customer questionnaires a year would struggle to justify the spend.

Every firm faces the same underlying constraint, whichever ERP it runs. An emissions figure depends on the activity data behind it, and most of that data already passes through the ERP: fuel and electricity invoices, freight bills, and purchases of materials by supplier and quantity. Many organisations record those transactions in dollars only, in catch-all expense codes, with no litres, kilowatt-hours or kilograms attached. A sustainability product on top of poorly coded transactions produces poorly founded numbers faster. Fixing the coding in the ERP itself is cheaper than any licence, and it pays off whether a firm later buys Microsoft's product, a specialist carbon tool or nothing at all.

Practical next steps

• Ask your largest customers, especially any Australian Group 2 companies, what emissions data they'll want from you, in what format and by when. Then build the answer once and reuse it.
• Review your chart of accounts and item master for emissions-relevant spend such as electricity, fuel, freight, refrigerants and key raw materials. Add a quantity field (kWh, litres, kilograms, tonne-kilometres) to those purchase lines.
• Ask your own suppliers for product carbon footprints or emissions factors and store them against supplier and item records, so the data sits where purchasing staff already work.
• If you run Dynamics 365 Finance and you're a reporting entity, ask Microsoft or your partner for green ledger timing and a Dataverse storage estimate before you commit budget for the 2027 financial year.
• If you run Business Central or another ERP, cost Dynamics 365 Sustainability against a specialist carbon tool fed by ERP exports. Include Dataverse capacity and consumption-billed AI in the comparison.
• Name one owner across finance and operations for emissions data quality, and automate the collection of meter readings and freight data wherever a feed already exists.