New: Odoo and Dynamics 365 cost calculators.Estimate your costs

ERP vendors and the SLA terms that decide support after go-live

As of October 2026, Business Central, Finance, and Sales credit 25% of fees below 99.9% uptime. See support clocks, change notice, and post-go-live terms.

Both platformsImplementation & Go-Live16 min readUpdated 18 sources

Key takeaways

  • Scheduled downtime is excluded from Microsoft Downtime after at least five days’ notice.
  • Identify the app-specific downtime test and credit band, including Human Resources at 99.5% and 99%.
  • An ERP service level agreement is the clause that turns a publisher’s uptime and support language into a measurable commitment with a remedy.
  • Buyers often look for one document that covers the outage, the ticket, and the customization.

What ERP vendors owe after you buy

An ERP service level agreement is the clause that turns a publisher’s uptime and support language into a measurable commitment with a remedy. For Microsoft Dynamics 365 that remedy is a service credit under the Service Level Agreement for Online Services. The edition current as of October 2026 is the October 1, 2026 agreement. It covers Dynamics 365 among other online services. Microsoft says it will not change that SLA during the initial subscription term. The version current at renewal applies to the renewal term. Microsoft will give at least 90 days’ notice of adverse material changes to the SLA.

Directory roundups of top ERP vendors rank publishers by product breadth or estimated revenue. Apps Run The World estimated the worldwide ERP applications market at $145,582 million in 2025, up 11% from $131,643 million in 2024, and published those figures in August 2026. Its top five by estimated ERP application revenue were Oracle at $9,719 million (6.7%), SAP at $9,610 million (6.6%), Intuit at $6,497 million (4.5%), CSI Software at $5,841 million (4%), and Microsoft at $3,233 million (2.2%). Those figures are the analyst’s estimates. They do not say what the publisher owes a mid-market buyer when users cannot log in on a Monday.

For a US or Canadian finance lead, ERP vendor selection is the split between the publisher, the cloud host, and the firm that configured the system. The publisher SLA covers the platform definition of downtime and the credit or support clock written into that document. The implementing partner’s statement of work covers hypercare, custom code, and, for Business Central, the technical help Microsoft tells those customers to seek from the reseller. Read both before go-live. A revenue ranking will not tell you which one pays, or responds, when the close is stuck.

The publisher SLA, the support plan, and the partner statement of work

Buyers often look for one document that covers the outage, the ticket, and the customization. On Dynamics 365 those are three different writings. The October 2026 online-services SLA sets uptime bands and service credits. The support plan sets initial response by severity, and it is a separate page from the uptime SLA. The partner statement of work sets hypercare, custom code, integrations, and the day-to-day work Microsoft’s core support will hand back once it has evidence the cause is custom code, partner or ISV software, or the environment.

Odoo splits the same way. The Enterprise Subscription Agreement, version 13, dated September 24, 2026, is the contract: bug handling, what the subscription support includes, security-advisory notice on self-hosted covered versions, renewal limits, liability, and a 99.9% network uptime commitment for the cloud platform. The cloud SLA page repeats a 99.9% monthly target and then states that the uptime and recovery objectives are design goals and are not legally binding guarantees. If a partner implements the database, that partner is the main contact and Odoo is second-line for standard features.

Self-hosted Odoo adds a host. Odoo’s cloud backup and uptime pages apply to Odoo’s platform. A database on your own server, or on a host you contract, takes its infrastructure promise from that host. Odoo still has a support policy for covered versions of the software, including a security advisory at least two weeks before public disclosure of a security bug in covered versions, unless a third party has already disclosed it.

Which writing covers uptime, response, and your build, as of October 2026.
WritingOwed byWhat is measurableRemedy you can point to
Online Services SLA, October 1, 2026MicrosoftDowntime by app, in user-minutes, with scheduled downtime excludedService credit, sole remedy, capped at that service’s monthly fees
Dynamics 365 support planMicrosoftInitial response by severity and planIncluded standard support, or a paid plan where the product is eligible
Partner statement of workImplementerHypercare, custom code, Business Central technical helpThe fees and clocks written in that statement of work
Enterprise Subscription Agreement v13, September 24, 2026OdooBug handling starts within 2 business days; cloud network uptime stated at 99.9%Liability of each party capped at 50% of amounts paid in the prior 12 months
Odoo cloud SLA pageOdoo99.9% monthly target, described as 45 minutes of unplanned downtimePage says the target and recovery objectives are not legally binding guarantees

What SLAs to expect from cloud ERP vendors for uptime

Cloud ERP vendors do not share one uptime clause. As of October 2026, Dynamics 365 Business Central treats downtime as any period when end users cannot log in to their instance. Finance, Supply Chain Management, and Project Operations share a downtime test of inability to log in to an Active Tenant because of a failure in the unexpired Platform or Service Infrastructure, as Microsoft determines from health monitoring and logs. Sales Enterprise and Sales Professional, Customer Service Enterprise and Professional, Field Service, and Marketing use a different test: inability to read or write service data the user is permitted to access. Human Resources uses a lower credit threshold, described in the next section.

Scheduled downtime is defined out of Microsoft’s Downtime. Microsoft defines Scheduled Downtime as network, hardware, or service maintenance or upgrades, and says it will publish notice or notify the customer at least five days before that downtime starts. A 99.9% calculation on these apps is therefore an unplanned-downtime figure. Previews, pre-release, beta, and trial services sit outside the SLA and are not eligible for claims or credits.

Odoo’s cloud SLA page states a 99.9% monthly uptime target, excluding planned maintenance, and says that equals a maximum of 45 minutes of unplanned downtime per month. Planned maintenance is typically less than one hour, roughly every couple of months, outside regional business hours, and is announced by email or @OdooStatus. The Enterprise agreement says Odoo commits to at least three hosting regions (Europe, America, Asia/Pacific), Tier-III or equivalent data centers, 99.9% network uptime, HTTPS, automated backups replicated in multiple regions, and a regularly tested disaster-recovery plan. Read that commitment next to the cloud page’s statement that the uptime and recovery objectives are design goals and are not legally binding guarantees.

Finance and operations apps have a separate maintenance practice inside the service updates. Microsoft says expected downtime for a successful update is about 15 minutes and asks for a three-hour window in case the update fails. Customers set the day and the maintenance window in Lifecycle Services. That seven-day sandbox lead time, covered under platform changes below, applies to finance and operations apps. It is not the Business Central rule. Business Central follows the general five-day Scheduled Downtime notice in the online-services SLA.

Published uptime tests for Dynamics 365 and Odoo cloud, October 2026. Credit percents are shares of applicable service fees, not cash.
ProductWhat counts as downtimeCredit or targetCarved out
Business CentralEnd users cannot log in to their instance25% under 99.9%, 50% under 99%, 100% under 95%Scheduled downtime
Finance, Supply Chain Management, Project OperationsCannot log in to an Active Tenant because of unexpired platform or service infrastructure, as Microsoft determines25% under 99.9%, 50% under 99%, 100% under 95%Scheduled downtime, add-ons, customer modifications, Scale Unit capacity exceeded
Sales, Customer Service, Field Service, MarketingCannot read or write service data the user may access25% under 99.9%, 50% under 99%, 100% under 95%Add-on features
Human ResourcesSee the October 2026 SLA table for that app25% under 99.5%, 50% under 99%The table shown does not list a 100% band
Odoo cloudUnplanned time against a 99.9% monthly target45 minutes stated as the monthly maximum for that targetPlanned maintenance; page says the target is not a legally binding guarantee

Incident uptime band reporting and when credits start

Incident uptime band reporting on Dynamics 365 is the monthly comparison of measured uptime to three bands, then a credit if the customer claims it in time. For Business Central, Finance, Supply Chain Management, Project Operations, Sales, Customer Service, Field Service, and Marketing, the October 2026 bands are 25% of applicable service fees if uptime is under 99.9%, 50% if under 99%, and 100% if under 95%. Human Resources credits 25% below 99.5% and 50% below 99%. The October 2026 table shown for Human Resources does not list a 100% band.

Business Central downtime is measured in user-minutes: incident length times users affected. Assume 40 users cannot log in for 30 minutes. That incident is 1,200 user-minutes. Microsoft compares user-minutes of downtime with user-minutes in the period, and user-minutes exclude scheduled downtime. The figures a buyer can apply are that user-minute unit, the exclusion of scheduled downtime, and the three credit bands. Finance and operations downtime is what Microsoft determines from health monitoring and logs, which means a local symptom that those logs do not class as a platform failure can fall outside the credit.

For non-Azure Microsoft online services, a service-credit claim must arrive by the end of the calendar month after the month of the incident. Microsoft’s example is an incident on February 15, which must be claimed, with the required detail, by March 31. Credits are the sole remedy. The customer may not unilaterally offset fees. Credits in a billing month cannot exceed that service’s monthly fees. A 25% band on a service whose applicable monthly fee is $4,000 is a $1,000 credit against that service, not a payment for late shipments or a delayed close. Put the claim date on the finance calendar in the month after any incident you believe crossed a band.

Odoo publishes the 99.9% figure and the 45-minute translation, and it does not publish a 25/50/100 credit ladder on the cloud SLA page. The same page says the uptime and recovery objectives are design goals and are not legally binding guarantees. Treat a missing credit table as a missing remedy. The money clause that is in the Enterprise agreement is the liability cap: aggregate liability of each party is capped at 50% of the amounts the customer paid under the agreement in the 12 months before the claim. The agreement is governed by Belgian law, with exclusive jurisdiction of the Nivelles Business Court.

[[embed {"type":"money","href":"/services/erp","title":"Scope the support writing before you sign","body":"Flectic's delivery method is designed to deliver up to 3x faster. A support scoping call lines up the October 2026 Microsoft credit bands, the Odoo agreement versus the cloud page, and the partner terms for custom code and Business Central.","cta":"Book a free discovery call"}]]

How a credit is earned on Microsoft online services other than Azure, October 2026 edition.
StepRuleWorked case
MeasureUser-minutes equal incident length times users affected. Scheduled downtime is excluded.40 users, 30 minutes: 1,200 user-minutes
BandUnder 99.9% pays 25%, under 99% pays 50%, under 95% pays 100%, for the apps that use that ladder. Human Resources starts at under 99.5%.A month that lands at 99.4% on Business Central is in the 25% band
ClaimClaim by the end of the next calendar month, with the detail Microsoft requires.February 15 incident: claim by March 31
CapSole remedy. Credits cannot exceed that service’s fees for the billing month. The customer may not offset fees on their own.$4,000 applicable monthly fee at 25% is a $1,000 credit

Support response times to expect from cloud ERP vendors

Uptime credits and support response are different clocks. Dynamics 365 and Power Platform standard support initial response, as of October 2026, is under 1 hour for Severity A on a 24x7 basis, under 4 hours for Severity B, and under 8 hours for Severity C. Professional Direct and Unified enterprise are under 1 hour for Severity A, under 2 hours for Severity B, and under 4 hours for Severity C. Severity A and B are 24x7 in English. Other listed languages are local business hours.

Microsoft describes Severity A as critical business impact: the customer’s business has significant loss or degradation of services and requires immediate attention. Severity B is moderate business impact: moderate loss or degradation, while work can reasonably continue in an impaired manner. These are initial-response targets. They are not a promise of a restored close, a restored warehouse, or a root-cause report. In North America, Microsoft support business hours are 6:00 a.m. to 6:00 p.m. Pacific time, Monday to Friday, excluding holidays.

Microsoft may downgrade severity if the customer cannot stay engaged. It may also downgrade requests for root-cause analysis, customized processes or code, and tickets waiting on the customer. Technical support does not conduct root-cause analyses. When an RCA is produced, it comes from engineering for published multi-customer service incidents, in English. On a break-fix performance case the Dynamics support team invests up to four hours. If the case is still unresolved, the incident is closed and the customer is pointed to a partner or the community, unless Premier or Unified can continue as advisory.

Odoo’s subscription clock is different. Version 13 of the Enterprise agreement says Odoo will start handling bug submissions within 2 business days. The US pricing page says Standard and Custom plans include email support Monday to Friday, 24/5, in English, French, Spanish, or Dutch. That is a start-work and channel commitment for covered bugs and standard-feature guidance. It is not a severity matrix with a one-hour critical response.

Initial response targets for Dynamics 365 and Power Platform support, as published for October 2026. These are response clocks, not resolution clocks.
PlanSeverity ASeverity BSeverity C
Standard, included with a Dynamics 365 purchaseUnder 1 hour, 24x7Under 4 hoursUnder 8 hours
Professional Direct and Unified enterpriseUnder 1 hour, 24x7Under 2 hoursUnder 4 hours
Language coverageSeverity A and B are 24x7 in EnglishOther listed languages follow local business hoursNorth America business hours are 6:00 a.m. to 6:00 p.m. Pacific, Monday to Friday, excluding holidays

Where a ticket goes when the publisher stops

Creating a Dynamics 365 or Power Platform support request requires an active support plan. Standard subscription support is included with a Dynamics 365 purchase. Professional Direct is listed at USD 9.00 per user per month, paid yearly, with a minimum of 20 users. At that minimum, 20 users is USD 180 per month and USD 2,160 for the year before tax. Microsoft’s support page says Professional Direct does not cover Business Central, and it describes standard support as the fit for a simple environment or for a business using a full-service partner. Unified Enterprise is custom-priced.

Business Central customers are told to contact their reselling partner for technical problems. That sentence is the escalation path for BC: the partner is first-line, and Microsoft’s paid Professional Direct plan is not the product you add to change that. Write the partner’s names, after-hours route, and what happens when the partner needs a Microsoft ticket into the statement of work. Ask whether your partner clock keeps running while a publisher ticket is open. A clock that stops at “escalated” leaves a Severity A incident with the publisher’s initial-response target and no separate promise on the custom work.

On Odoo, if the customer uses a partner, that partner is the main contact and Odoo is second-line for standard features. Direct Odoo support for covered extra modules is available only if the customer is on the Odoo cloud platform. Development and customization questions need a separate service agreement. Name the partner contact who will open the Odoo ticket, and name the customer contact who can stay engaged, because a publisher can downgrade or pause work when the customer side goes quiet. Microsoft states that downgrade rule in its support overview. Odoo’s agreement makes the partner the front door.

  1. Confirm the plan matches the product

    Standard support comes with a Dynamics 365 purchase and still requires an active support plan to open a request. Professional Direct at USD 9.00 per user per month does not cover Business Central. Unified Enterprise is custom-priced. Business Central technical problems go to the reselling partner.

  2. Name the people on the partner path

    Put a primary contact and an after-hours contact in the statement of work, plus who opens the publisher ticket. For Odoo, the partner is the main contact and Odoo is second-line for standard features.

  3. Decide whether your clock pauses

    Publisher initial-response times are not your partner’s resolution times. Write whether the partner clock continues while Microsoft or Odoo investigates standard code, and who tells finance if a credit claim must be filed by the end of the following calendar month.

Advance notice of platform changes to look for in the SLA

The notice clauses to look for are dated, and they differ by product. On the Microsoft SLA itself, the customer gets at least 90 days’ notice of adverse material changes to the SLA, and the SLA does not change during the initial subscription term. Scheduled downtime, which is maintenance or upgrades of network, hardware, or service, gets at least five days’ notice and is excluded from Downtime. Those two clocks are the platform-wide rules in the October 1, 2026 agreement.

Finance and operations apps add a release calendar. They ship four service updates a year, in February, April, July, and October. Each release lifecycle is 404 to 414 days. Customers may pause only one update, so at least two service updates a year are required. Breaking changes are communicated 12 months ahead and are introduced only in the April and October major updates. New experiences are opt-in for 12 months. Deprecation of a feature is announced 12 months before removal. The designated UAT sandbox is updated seven calendar days before production. Sandbox issues can support a request to skip an update only with a support ticket number and a business justification. Expected downtime on a successful update is about 15 minutes, inside a three-hour window the customer sets in Lifecycle Services.

Odoo’s notice rules sit in the Enterprise agreement and the cloud page. A new major version ships once a year. Covered versions are the three most recent major versions. For self-hosted Odoo, Odoo sends a security advisory at least two weeks before public disclosure of a security bug in covered versions, unless a third party has already disclosed it. On the cloud platform, Odoo applies the remedy itself when it is available. Planned maintenance is announced by email or @OdooStatus and is typically under an hour, roughly every couple of months, outside regional business hours. Renewal fees can rise by up to 7% per year of the previous term if the prior charges were below the then-current list price. A database older than the covered versions can incur an extra fee equal to 25% of the annualized price, once a year, and no earlier than six months after a new major release.

Use the finance and operations dates for those apps only. Do not copy the seven-day sandbox rule onto Business Central. For BC, the sourced advance-notice figure in the October 2026 SLA is the five-day Scheduled Downtime notice, plus the 90-day notice if Microsoft makes an adverse material change to the SLA.

Advance notice a buyer can cite, as of October 2026. Finance and operations rules do not transfer to Business Central.
EventNoticeWhere it applies
Adverse material change to the Microsoft SLAAt least 90 daysOnline Services SLA; no SLA change during the initial term
Microsoft scheduled downtimeAt least 5 daysNetwork, hardware, or service maintenance or upgrades; excluded from Downtime
Finance and operations service updatesFour a year: February, April, July, October; only one pauseSandbox updates 7 calendar days before production
Breaking change, new experience, deprecation12 monthsBreaking changes only in April and October; new experiences opt-in for 12 months
Odoo security bug, self-hosted covered versionsAt least 2 weeks before public disclosureUnless a third party already disclosed it; cloud applies the remedy itself
Odoo price at renewalUp to 7% over the previous term if prior charges were below listPlus 25% of annualized price, once a year, if the database is older than covered versions

What the uptime math leaves out

The credit bands only pay for downtime as the publisher defines it. On Business Central, downtime is inability to log in. On Finance, Supply Chain Management, and Project Operations, the definition excludes scheduled downtime, add-on features, customer modifications, and periods when Scale Unit capacity is exceeded. A tenant that has outgrown its scale unit can be down from the user’s point of view and still sit outside the credit. Sales, Customer Service, Field Service, and Marketing exclude add-on features, and their test is read and write of permitted data, so a slow screen that still reads and writes can miss the definition.

Custom code, partner or ISV software, and environmental causes fall outside Microsoft core support once that cause is evidenced. A break-fix performance case gets up to four hours from the Dynamics support team, then closure toward a partner or community unless Premier or Unified continues as advisory. Previews, betas, and trials are outside the SLA entirely. Microsoft may also downgrade severity when the customer cannot stay engaged, when the request is for root-cause analysis, or when the request is about customized processes or code.

Odoo subscription support is unlimited tickets only for bugs and guidance on standard features of the software and covered extra modules. Implementation, expert services, Odoo.sh hosting for custom developments, and maintenance of custom code are excluded from the Standard and Custom plans on the US pricing page. Companies under 50 employees are pointed to Success Packs. Companies over 50 employees are pointed to partners. The cloud uptime target excludes planned maintenance. Customers cannot choose or restrict backup regions, which matters for a Canadian company that wanted backups kept only in Canada: replicas include Europe and Canada, and region choice is not a customer setting.

  • Scheduled downtime is excluded from Microsoft Downtime after at least five days’ notice.
  • Customer modifications, add-ons, and exceeded Scale Unit capacity are excluded on finance and operations apps.
  • Standard Microsoft support stops at evidenced custom code, ISV software, and environmental causes, and it does not write root-cause analyses.
  • Odoo subscription support excludes implementation, custom-code maintenance, and Odoo.sh hosting for custom developments.
  • Odoo’s 45-minute figure excludes planned maintenance and, on the cloud SLA page, is not a legally binding guarantee.

Security and change notice the contract states

Ask for the notice window in the document that governs that event, and keep the windows separate. The October 2026 Microsoft SLA states two of them: at least 90 days for an adverse material change to the SLA, and at least five days before scheduled downtime. It also states that the SLA version is stable during the initial subscription term and that renewal uses the version current at renewal. Those 90-day and five-day notices cover SLA changes and scheduled downtime. The October 2026 SLA does not state a personal-data breach hour count.

Odoo’s sourced security notice is the self-hosted advisory: at least two weeks before public disclosure of a security bug in covered versions, unless a third party has already disclosed it. Covered versions are the three most recent major versions. On the cloud platform, Odoo applies the remedy itself when it is available, so the customer’s action is to know the maintenance announcement channel, which is email or @OdooStatus. Odoo’s data-protection wording says it will notify the customer promptly after confirming unlawful processing. That sentence does not state an hour count. Put any tighter clock you need in the customer contract you negotiate with the partner, and keep the publisher’s “promptly” language visible so the two are not confused.

Finance and operations customers also have a 12-month notice for breaking changes and for feature removal, with breaking changes landing only in April and October. That is product-change notice, not incident notice. A practical pack for the statement of work is a named security contact, a requirement that the partner forward publisher advisories the day they arrive, and a rule for how custom code is checked against a finance and operations sandbox that updates seven calendar days before production. The publisher clocks above are the ones you can cite without adding an hour figure the contract does not contain.

Renewal, liability, backups, and leaving

Microsoft’s credit clause shapes the upside of an uptime dispute. Credits are the sole remedy, the customer may not unilaterally offset fees, and credits in a billing month cannot exceed that service’s monthly fees. If the relationship has to end over repeated missed bands, that right has to be in the agreement you sign with Microsoft’s licensing channel or with the partner. The online-services SLA itself presents the credit as the remedy for the uptime commitment.

Odoo’s exit economics are more explicit. Renewal can rise by up to 7% per year of the previous term when prior charges were below the then-current list price. A database older than the three covered major versions can add a fee equal to 25% of the annualized price, once a year, no earlier than six months after a new major release. Aggregate liability of each party is capped at 50% of amounts the customer paid under the agreement in the 12 months before the claim. Disputes go to Belgian law and the Nivelles Business Court. A Canadian buyer should read that forum clause with counsel before treating the cloud page as a local service commitment.

Backup location is part of exit and of residency. Odoo keeps 14 full backups for at least 3 months, on a pattern of daily for 7 days, weekly for 4 weeks, and monthly for 3 months or more. They are replicated on at least three machines in different data centers in Europe and Canada, plus a fourth immutable cold copy. Customers cannot choose or restrict backup regions. Disaster-recovery objectives on the cloud page are design goals: single-server permanent disaster RPO 24 hours, with near zero expected for Odoo SaaS, and RTO 6 hours; full data-center disaster RPO 24 hours and RTO 24 hours. Because the page says those objectives are not legally binding guarantees, a customer that needs a contractual restore time has to place that time in a separate service agreement.

On the US price page, Standard displays USD 24.90, USD 31.10, and USD 38.90 per user per month, with yearly and monthly toggles, and a footnote that the discount is valid for 12 months for the initial users ordered. Custom displays USD 49.00, USD 61.00, and USD 76.20, and a light user at USD 8.90. Odoo.sh hosting is extra on Custom. The page does not display a CAD list price. If the rate that applies is the USD 24.90 Standard figure, 30 users is USD 747 per month before a later renewal change. Run the same multiplication on the figure your order form uses. Success Packs, below, are the published hour bundles, and they are not a substitute for an export clause in the partner agreement.

Clauses worth locking before signature

The publisher documents are mostly standard terms. The room to write is the partner statement of work and any service agreement for custom code. Ask for five items in writing. First, which system is in scope, because Professional Direct does not cover Business Central and Business Central customers are directed to the reseller. Second, the severity words you will use, mapped to Microsoft’s Severity A, B, and C where the ticket will be handed to Microsoft, so a “critical” label in the statement of work is not a different event from Microsoft’s critical business impact. Third, whether the partner clock pauses while the publisher investigates standard code. Fourth, who files a Microsoft credit claim by the end of the calendar month after the incident. Fifth, a renewal cap you can live with. Odoo’s own cap, when prior charges are below list, is up to 7% a year.

Price the support you are buying. Standard Microsoft response is included with a Dynamics 365 purchase if a support plan is active. Professional Direct at USD 9.00 per user per month, yearly, minimum 20 users, changes the Severity B clock from under 4 hours to under 2 hours and Severity C from under 8 hours to under 4 hours, and it still does not cover Business Central. Unified Enterprise is custom-priced. On Odoo, subscription email support is Monday to Friday, 24/5, and bug handling starts within 2 business days, for bugs and standard features.

Keep claims and credits on a calendar. For a February 15 Microsoft incident the claim deadline in the publisher’s example is March 31. Credits do not arrive because the status page was wrong. Someone has to submit the detail. For Odoo, do not enter a negotiation assuming a 25% credit at 99.9%. The cloud page does not offer that ladder, and it says the target is not legally binding. If you need a money remedy, it has to be drafted. The liability cap already in the Enterprise agreement is 50% of the prior 12 months’ payments.

The written proposal sets the timeline and a fixed price for each phase before work starts, and the delivery method is designed to deliver up to 3x faster. Support terms belong in that proposal, not in a later argument. The scoping conversation is the place to line up the October 2026 Microsoft bands, the Odoo agreement versus the cloud page, and the partner statement of work for custom code and Business Central.

Decision criteria before you sign. Publisher columns are October 2026 published terms. Partner column is what you still have to write.
DecisionMicrosoft, October 2026Odoo, agreement v13 and cloud pageWrite into the partner document
Uptime remedy25/50/100 credit ladder on the main apps; Human Resources 25/50 from 99.5/9999.9% in the agreement; 45-minute design target on the cloud page, not a credit ladderWho watches the month and files any Microsoft claim
ResponseStandard under 1/4/8 hours for A/B/C; Professional Direct and Unified under 1/2/4Bug handling starts within 2 business days; email Monday to Friday 24/5Your resolution targets for custom code and hypercare
Business CentralContact the reselling partner; Professional Direct does not cover BCNot a Business Central productNamed partner contacts and after-hours path
Platform change90 days for adverse SLA changes; 5 days for scheduled downtime; finance and operations sandbox 7 days before production2 weeks’ security advisory on self-hosted covered versions; cloud applies the fixWho tests the sandbox and who may request a skip
Price pathProfessional Direct USD 9 per user per month, yearly, 20-user minimum; Unified customRenewal up to 7% if below list; 25% annualized extra if the database is outside covered versionsAny cap you need that is tighter than the publisher’s

How the two publisher SLAs differ

Dynamics 365, under the October 1, 2026 online-services SLA, gives a credit ladder on defined downtime and a separate support-plan response table. The credit is the sole remedy, claimed by the end of the following calendar month, and it never exceeds that service’s monthly fees. Standard support is included with the purchase if the support plan is active. Professional Direct costs USD 9.00 per user per month and does not cover Business Central. Technical support will not do a root-cause analysis, and a performance break-fix stops at four hours unless a higher plan continues as advisory. Finance and operations customers live on four updates a year and can pause only one.

Odoo Enterprise version 13, dated September 24, 2026, includes unlimited tickets for bugs and standard-feature guidance, with work starting within 2 business days, and it states a 99.9% network uptime commitment for the cloud platform along with three regions, Tier-III or equivalent data centers, HTTPS, replicated backups, and a tested disaster-recovery plan. The cloud SLA page then says the 99.9% target, the 45-minute equivalent, and the RPO and RTO figures are design goals and are not legally binding guarantees. That conflict is the point to resolve in procurement. Section 4.4 of the agreement is a commitment. The cloud page tells the reader not to treat the same numbers as a guarantee. A buyer should not paste the marketing SLA into a board pack as if it were a credit clause.

Support scope follows the same split. Microsoft core support, once a custom, partner, ISV, or environmental cause is evidenced, points the customer to a partner. Odoo requires a separate service agreement for development and customization, and it makes the partner the main contact when one is involved. Direct support on covered extra modules requires Odoo cloud. Companies under 50 employees are pointed to Success Packs on the pricing page. Companies over 50 employees are pointed to partners. For a 60-person company, plan on a partner for implementation and for custom code, and use Odoo as second-line for standard features.

Canada shows up in Odoo’s backup design, not in a special uptime percent. Backups replicate to data centers in Europe and Canada, and the customer cannot restrict regions. The contract forum is the Nivelles Business Court under Belgian law. The US pricing page does not show a CAD list price. Compare the two publishers on the remedy you can file, the response clock you can quote, and the change notice you can diary. A market-share table will not make that comparison.

Post-implementation support to expect from ERP vendors

Post-implementation support from ERP vendors is three layers, and only one of them is the subscription. The subscription layer is break-fix on the standard product. On Dynamics 365 that is the support plan you already have: Severity A under 1 hour on standard, Severity B under 4 hours, Severity C under 8 hours, English 24x7 for A and B, North American business hours 6:00 a.m. to 6:00 p.m. Pacific on weekdays for the hours that are not 24x7. On Odoo it is unlimited tickets for bugs and guidance on standard features and covered extra modules, with Odoo starting to handle bug submissions within 2 business days. Covered extra modules get direct Odoo support only on Odoo cloud.

The second layer is paid publisher time that is not hypercare. Odoo Success Packs for a new customer are USD 493, USD 3,060, USD 5,950, USD 10,625, and USD 21,250 for 4, 25, 50, 100, or 200 dedicated consultant hours, with 15% off the first pack. Returning-customer prices on the same table are USD 580, USD 3,600, USD 7,000, USD 12,500, and USD 25,000. Onsite travel is billed extra. These packs are Odoo’s own hour bundles, separate from a hypercare clause and from an independent partner’s rate card. Performance work at Odoo requires a Success Pack of at least 50 hours, which is the USD 5,950 new-customer pack before the 15% first-pack reduction. A 15% reduction on USD 5,950 is USD 5,057.50 if that pack is the first one.

The third layer is the partner after go-live: hypercare, custom-code fixes, integrations, and Business Central technical problems. Microsoft tells Business Central customers to contact the reselling partner. Microsoft technical support invests up to four hours on a break-fix performance case and then points to a partner or community unless Premier or Unified continues as advisory. Odoo excludes implementation and maintenance of custom code from the subscription, and it excludes Odoo.sh hosting for custom developments. There is no publisher price list for an independent partner’s retainer. The number you will pay lives in that firm’s statement of work.

A workable first month after go-live names which layer owns each ticket. A login outage is a publisher uptime and Severity A event, a standard Odoo bug starts with the partner then Odoo within 2 business days, and a customization is partner work or a Success Pack.

Typical support options and SLAs included with the subscription

Typical support included with an ERP subscription is narrower than the sales conversation. With Dynamics 365, the included piece is standard subscription support: an active support plan is required to open a request, and the initial response targets are under 1 hour, under 4 hours, and under 8 hours for Severity A, B, and C. The included uptime remedy, for the apps on the main ladder, is the 25%, 50%, and 100% credit schedule under 99.9%, 99%, and 95%. Professional Direct is optional, at USD 9.00 per user per month, and the page says it does not cover Business Central. Unified Enterprise is optional and custom-priced.

With Odoo Standard and Custom, the US pricing page includes hosting, backups, 24/7 monitoring, email support Monday to Friday 24/5 in English, French, Spanish, or Dutch, and upgrades. The Enterprise agreement adds the bug-handling start within 2 business days and unlimited tickets for bugs and standard-feature guidance, including covered extra modules on the terms above. The same pricing page excludes implementation, expert services, Odoo.sh hosting for custom developments, and maintenance of custom code. Hosting commitments in the agreement include 99.9% network uptime, at least three regions, Tier-III or equivalent data centers, HTTPS, and replicated backups. The cloud page’s 14 backups, kept at least 3 months, and the RPO and RTO figures sit beside the non-binding statement.

Assume a 25-person US company on Odoo Standard. If the order uses the USD 24.90 figure shown on the card, 25 users cost USD 622.50 per month. That fee includes the monitoring, backups, email support window, and upgrades described above. It does not include a 50-hour performance pack (USD 5,950 before the new-customer 15% reduction) or a partner’s hypercare week. Assume the same headcount on Dynamics 365 with standard support included. Adding Professional Direct for 25 users, above the 20-user minimum, is 25 times USD 9.00, which is USD 225 per month, paid yearly, and only if the apps on the tenant are products that plan covers. It does not add Business Central coverage.

Companies under 50 employees see Success Packs on Odoo’s pricing guidance. Companies over 50 employees see a partner. A firm of 80 people should budget partner time for rollout and for custom code, and should treat Odoo’s 2-business-day bug start as the publisher layer under that partner. The same firm on Dynamics 365 should budget the partner for configuration and for anything Microsoft classes as custom code, and should keep the credit-claim calendar even though standard response is included.

What the subscription includes, as of the October 2026 sources. CAD list prices are not on the Odoo US price page.
Included itemDynamics 365Odoo Standard and Custom
Uptime writingOctober 1, 2026 Online Services SLA, credit bands by appAgreement states 99.9% network uptime; cloud page states a 45-minute design target
Support channelSupport request on an active plan; standard response under 1/4/8 hoursEmail Monday to Friday 24/5; bug handling starts within 2 business days
Backups and monitoringPlatform terms in the Microsoft SLA and product docs24/7 monitoring; 14 full backups kept at least 3 months; replicas in Europe and Canada
Explicitly extraProfessional Direct USD 9 per user per month where eligible; Unified custom; partner for BC and custom codeImplementation, expert services, custom-code maintenance, Odoo.sh for custom developments, Success Pack hours
Who is first contactMicrosoft, except Business Central customers contact the reselling partnerOdoo, unless a partner is engaged, in which case the partner is first and Odoo is second-line for standard features

ERP vendor SLA checklist

Use this list while the order form is still open. Confirm which of the three writings you hold: the October 1, 2026 Microsoft Online Services SLA or Odoo Enterprise version 13 dated September 24, 2026; the support plan or the cloud SLA page; and the partner statement of work. Confirm the downtime test for the app you bought, because Business Central, finance and operations, Sales, and Human Resources do not use one identical credit table.

Diary the notice dates that match the product. Microsoft: 90 days for an adverse SLA change, five days for scheduled downtime, and, for finance and operations only, a sandbox seven calendar days before production, four updates a year, and one pause. Odoo: two weeks before public disclosure of a self-hosted security bug in covered versions, planned maintenance announced by email or @OdooStatus, and a renewal that can move by up to 7% if you were below list. Diary the Microsoft claim date, which is the end of the calendar month after the incident month.

Match people to exclusions. Name who files credits, who stays engaged so Microsoft does not downgrade severity, and who owns custom code after the four-hour performance cap or after Odoo’s subscription exclusions. If the company is in Canada and data residency matters, record that Odoo backup regions include Europe and Canada and cannot be restricted by the customer, and that the Enterprise agreement uses Belgian law and the Nivelles Business Court. If you want a tighter restore promise than RPO 24 hours and RTO 24 hours for a data-center disaster, that promise has to be written somewhere other than the cloud page, because that page calls the figures design goals.

Flectic scopes both the publisher terms and the partner statement of work for Microsoft Dynamics 365 and Odoo implementations aimed at companies of 20 to 100 people in the US and Canada. Bring the order form, the support-plan name, and the draft statement of work to a support scoping call if you want those clocks checked against the October 2026 documents before you sign.

  • Identify the app-specific downtime test and credit band, including Human Resources at 99.5% and 99%.
  • Separate scheduled downtime (five days’ notice, excluded) from unplanned downtime that can earn a Microsoft credit.
  • Write the claim owner and the March 31-style deadline for a mid-month incident.
  • Confirm Business Central is on the partner, and that Professional Direct is not being bought for BC.
  • Confirm whether Odoo support is direct or through a partner, and whether custom code has a Success Pack or a separate agreement.
  • Record finance and operations update dates only for those apps: February, April, July, October, one pause, 12-month breaking-change notice.
  • For Canada, record Odoo backup regions and the Nivelles forum before you rely on the 99.9% sentence.

How Flectic can help

Flectic implements Odoo or Dynamics 365 for companies of 20 to 100 people, and a named senior consultant leads your project from discovery to launch stabilization. Our Core Odoo industry package includes 30 business days of launch stabilization with up to 10 advisory hours. Book a free discovery call with Flectic to review the support terms in your vendor and partner contracts against our ERP implementation scope.

Sources

  1. The current Microsoft Service Level Agreement for Online Services is the October 1, 2026 edition and covers Dynamics 365. Microsoft will not change the SLA during the initial subscription term; the version current at renewal applies to the renewal term; at least 90 days’ notice of adverse material changes.

    microsoft.comChecked 2026-10
  2. Scheduled Downtime is network, hardware, or service maintenance or upgrades. Microsoft gives at least five days’ notice and excludes scheduled downtime from Downtime.

    microsoft.comChecked 2026-10
  3. For non-Azure Microsoft online services, a service-credit claim must arrive by the end of the calendar month after the incident month. A February 15 incident must be claimed by March 31. Credits are the sole remedy, may not be unilaterally offset, and cannot exceed that service’s monthly fees.

    microsoft.comChecked 2026-10
  4. Business Central downtime is any period when end users cannot log in. Credits are 25% under 99.9%, 50% under 99%, and 100% under 95%, measured in user-minutes (incident length times users affected).

    microsoft.comChecked 2026-10
  5. Finance, Supply Chain Management, and Project Operations use the same 25/50/100 ladder below 99.9/99/95. Downtime is inability to log in to an Active Tenant because of a failure in the unexpired Platform or Service Infrastructure, excluding scheduled downtime, add-ons, customer modifications, and periods when Scale Unit capacity is exceeded.

    microsoft.comChecked 2026-10
  6. Sales Enterprise and Professional, Customer Service Enterprise and Professional, Field Service, and Marketing use the 25/50/100 ladder. Downtime is inability to read or write permitted service data and excludes add-on features.

    microsoft.comChecked 2026-10
  7. Dynamics 365 Human Resources credits 25% below 99.5% and 50% below 99%. The October 2026 table shown does not list a 100% band.

    microsoft.comChecked 2026-10
  8. Previews, pre-release, beta, and trial services are outside the Microsoft SLA and are not eligible for claims or credits.

    microsoft.comChecked 2026-10
  9. October 2026 English SLA file is the current edition on Microsoft’s SLA index.

    microsoft.comChecked 2026-10
  10. Dynamics 365 and Power Platform standard initial response is under 1 hour for Severity A (24x7), under 4 hours for Severity B, and under 8 hours for Severity C. Professional Direct and Unified enterprise are under 1, 2, and 4 hours. Severity A and B are 24x7 in English; other listed languages are local business hours. North America business hours are 6:00 a.m. to 6:00 p.m. Pacific, Monday to Friday, excluding holidays. Microsoft may downgrade severity if the customer cannot stay engaged, and for root-cause analysis, customized processes or code, and tickets waiting on the customer.

    learn.microsoft.comChecked 2026-10
  11. Microsoft technical support does not conduct root-cause analyses. RCAs, when done, come from engineering for published multi-customer service incidents, in English. Break-fix performance work is capped at four hours, then the incident is closed toward a partner or community unless Premier or Unified continues as advisory. Custom code, partner or ISV software, and environmental causes are outside core support once evidenced.

    learn.microsoft.comChecked 2026-10
  12. A support request requires an active support plan. Standard subscription support is included with a Dynamics 365 purchase. Professional Direct is USD 9.00 per user per month, paid yearly, minimum 20 users, and does not cover Business Central. Business Central customers should contact the reselling partner. Unified Enterprise is custom-priced. Standard is described as the fit for a simple environment or a full-service partner.

    microsoft.comChecked 2026-10
  13. Finance and operations apps release four service updates a year (February, April, July, October). Each release lifecycle is 404 to 414 days. Customers may pause only one update. Breaking changes are communicated 12 months ahead and introduced only in April and October. New experiences are opt-in for 12 months. Deprecation is announced 12 months before removal. The UAT sandbox updates seven calendar days before production. Expected downtime is about 15 minutes inside a three-hour window. A skip requires a support ticket number and a business justification.

    learn.microsoft.comChecked 2026-10
  14. Odoo Enterprise Subscription Agreement version 13, dated 2026-09-24: bug submissions start within 2 business days; at least three hosting regions; Tier-III or equivalent data centers; 99.9% network uptime; HTTPS; replicated backups; tested disaster-recovery plan. Unlimited tickets only for bugs and standard-feature guidance. Partner is first-line when used. Direct support for covered extra modules only on Odoo cloud. Self-hosted security advisory at least two weeks before public disclosure unless already disclosed. Covered versions are the three most recent major versions; a new major version ships once a year. Renewal up to 7% if below list. Extra 25% of annualized price if the database is older than covered versions. Liability cap 50% of amounts paid in the prior 12 months. Belgian law and the Nivelles Business Court.

    odoo.comChecked 2026-10
  15. Odoo cloud SLA page: 99.9% monthly uptime excluding planned maintenance, equal to a maximum of 45 minutes of unplanned downtime per month. These uptime and recovery objectives are design goals, not legally binding guarantees. Planned maintenance is typically less than one hour, roughly every couple of months, outside regional business hours, announced by email or @OdooStatus. Single-server RPO 24 hours (near zero expected for Odoo SaaS) and RTO 6 hours; full data-center RPO 24 hours and RTO 24 hours. 14 full backups kept at least 3 months (daily 7 days, weekly 4 weeks, monthly 3+ months), replicated on at least three machines in Europe and Canada, plus a fourth immutable cold copy. Customers cannot choose or restrict backup regions.

    odoo.comChecked 2026-10
  16. Odoo US pricing page: Standard displays USD 24.90, 31.10, and 38.90 per user per month; Custom displays USD 49.00, 61.00, and 76.20; light user USD 8.90. Discount footnote is 12 months for initial users ordered. Standard and Custom include hosting, backups, 24/7 monitoring, email support Monday to Friday 24/5 in English, French, Spanish, or Dutch, and upgrades. Implementation, expert services, Odoo.sh for custom developments, and maintenance of custom code are excluded. Companies under 50 employees are pointed to Success Packs; companies over 50 employees are pointed to partners. CAD list price is not on this page.

    odoo.comChecked 2026-10
  17. Odoo Success Packs, new customers: USD 493, 3060, 5950, 10625, and 21250 for 4, 25, 50, 100, or 200 hours, with 15% off the first pack. Returning customers: USD 580, 3600, 7000, 12500, and 25000. Onsite travel is extra. Performance work requires a Success Pack of at least 50 hours. Packs are not a hypercare SLA.

    odoo.comChecked 2026-10
  18. Apps Run The World estimated worldwide ERP applications at $145,582 million in 2025, up 11% from $131,643 million in 2024. Estimated ERP application revenue: Oracle $9,719 million (6.7%), SAP $9,610 million (6.6%), Intuit $6,497 million (4.5%), CSI Software $5,841 million (4%), Microsoft $3,233 million (2.2%). Analyst estimates, published August 2026.

    appsruntheworld.comChecked 2026-10

Frequently asked questions

What SLAs should I expect from cloud ERP vendors for uptime and support response?

As of October 2026, Dynamics 365 Business Central, Finance, Supply Chain Management, Project Operations, Sales, and Customer Service use a credit of 25% of applicable fees under 99.9% uptime, 50% under 99%, and 100% under 95%. Standard support initial response is under 1 hour for Severity A, under 4 hours for Severity B, and under 8 hours for Severity C. Odoo’s Enterprise agreement states 99.9% network uptime and a start on bug submissions within 2 business days. Odoo’s cloud page describes 99.9% as 45 minutes of unplanned downtime a month and says that target is not a legally binding guarantee.

What are the typical support options and service level agreements included with an ERP subscription?

Dynamics 365 includes standard subscription support when the support plan is active, with the response times above, plus the online-services uptime credit schedule. Professional Direct is an add-on at USD 9.00 per user per month, paid yearly, minimum 20 users, and Microsoft says it does not cover Business Central. Odoo Standard and Custom include hosting, backups, 24/7 monitoring, weekday email support, and upgrades. Implementation, custom-code maintenance, and Odoo.sh hosting for custom developments are excluded and need a separate agreement or a Success Pack.

What post-implementation support should I expect from ERP vendors after go-live?

Expect the publisher to handle standard-product defects on its published clock, and expect custom work to sit with a partner or a paid hour pack. Odoo starts bug handling within 2 business days and limits subscription tickets to bugs and standard features. Microsoft’s Dynamics support team spends up to four hours on a break-fix performance case, then points to a partner or community unless Premier or Unified continues as advisory. Business Central customers are told to contact the reselling partner. Odoo Success Packs for new customers run from USD 493 for 4 hours to USD 21,250 for 200 hours.

What should I look for in vendor SLAs regarding advance notice of platform changes?

Microsoft gives at least 90 days’ notice of adverse material changes to the SLA and does not change the SLA during the initial subscription term. Scheduled downtime gets at least five days’ notice. Finance and operations apps update in February, April, July, and October, allow only one pause, warn of breaking changes 12 months ahead, and update the UAT sandbox seven calendar days before production. Odoo sends a self-hosted security advisory at least two weeks before public disclosure, unless a third party already disclosed the bug, and it can raise renewal fees by up to 7% a year if prior charges were below list.

How does incident uptime band reporting work, and when do service credits start?

Microsoft places the month on a band. Under 99.9% is a 25% credit, under 99% is 50%, and under 95% is 100% for the main Dynamics 365 apps listed in the October 2026 SLA. Human Resources credits 25% under 99.5% and 50% under 99%. Business Central uses user-minutes, incident length times users affected, and scheduled downtime is excluded. For non-Azure online services the claim must arrive by the end of the next calendar month. An incident on February 15 must be claimed by March 31. Odoo does not publish that credit ladder.

Does a 99.9% uptime promise include scheduled maintenance, and how many minutes is that per month?

Microsoft excludes Scheduled Downtime from Downtime. Scheduled Downtime is maintenance or upgrades, with at least five days’ notice, so the 99.9% band is an unplanned-downtime test. Odoo’s cloud page excludes planned maintenance from its 99.9% monthly target and says the target equals a maximum of 45 minutes of unplanned downtime per month. That page also says the figure is a design goal and is not a legally binding guarantee. Planned Odoo maintenance is typically under one hour, roughly every couple of months.

Is Business Central support included with Microsoft, or do I have to buy it from the partner?

Standard subscription support is included with a Dynamics 365 purchase, and opening a request still requires an active support plan. Microsoft’s support page tells Business Central customers to contact their reselling partner for technical problems. Professional Direct, at USD 9.00 per user per month with a 20-user minimum, does not cover Business Central. Unified Enterprise is custom-priced. Budget the partner statement of work for Business Central technical help rather than assuming the Professional Direct clock applies.

Does the publisher support customizations and performance issues, or only standard code?

Microsoft core support does not keep custom code, partner or ISV software, or environmental causes once those causes are evidenced. A break-fix performance case gets up to four hours, then the incident is closed toward a partner or community unless Premier or Unified continues as advisory. Technical support does not write root-cause analyses. Odoo subscription tickets cover bugs and guidance on standard features and covered extra modules. Development, customization, and maintenance of custom code need a separate service agreement. Odoo performance work requires a Success Pack of at least 50 hours.

How much notice do I get before a finance and operations update hits production?

The designated UAT sandbox is updated seven calendar days before production. Customers set the production day and the maintenance window in Lifecycle Services. Microsoft says expected downtime for a successful update is about 15 minutes and asks for a three-hour window in case the update fails. You can pause only one service update, and a skip based on sandbox issues needs a support ticket number and a business justification. This sandbox rule is for finance and operations apps. Business Central uses the five-day Scheduled Downtime notice instead.

Can I restrict where cloud ERP backups are stored if my company is in Canada?

On Odoo cloud, you cannot choose or restrict backup regions. Odoo keeps 14 full backups for at least 3 months and replicates them on at least three machines in different data centers in Europe and Canada, plus a fourth immutable cold copy. The Enterprise agreement is Belgian law, with exclusive jurisdiction of the Nivelles Business Court. If a Canadian residency rule requires a region lock, that lock is not a setting on this backup design, so it has to be solved with a different hosting arrangement.

More on the blog: Implementation and go-live