Responding to a Microsoft public tender in Québec: the essentials for 2026

The SEAO landscape in 2026

SEAO (Système électronique d'appel d'offres) is the single portal Québec public bodies use to publish their tenders. In 2026 it carries several thousand notices a year touching on IT advisory services, cloud infrastructure, cybersecurity, Microsoft 365 migration, and Copilot deployment.

For a private firm, responding to a SEAO tender is rarely intuitive. The rules aren't the ones you know from the private sector: administrative compliance sometimes carries as much weight as technical quality, public bodies require a documented decision trail (LCOP, LATMP, LCOP-OBNL), and the deadlines are strict.

This article sums up the essentials so you aren't disqualified the moment you submit - which happens more often than you'd think.

The Conseil du trésor general terms

Most Québec public bodies (ministries, municipalities, Crown corporations, the health network, the education network) rely on the general terms set by the Secrétariat du Conseil du trésor. Those terms impose a common framework, notably:

• A bid bond (often 1 to 5% of the estimated value) in the form of a certified cheque or a surety bond.
• An authorization to contract with a public body (AMP) for contracts above $1M.
• A valid Revenu Québec attestation as of the submission date.
• A commitment to comply with the Act respecting equal access to employment in public bodies.
• Compliance with the official-language requirements (deliverables in French, with conditions set by the public body).
• Without these administrative documents up to date, your bid is thrown out before the technical committee even opens it.

Law 25 requirements in 2026 public RFPs

Since Law 25 came into force, public RFPs systematically include clauses on the protection of personal information. What you absolutely have to demonstrate in your response:

• Your own organization's compliance with Law 25 (a designated privacy officer, a public privacy policy, a PIA for this engagement).
• A contractual commitment on the confidentiality, retention, and destruction of any personal information entrusted to you.
• A map of the subcontractors and third parties involved, along with their own compliance commitments.
• Data residency: Canada Central / Canada East hosting is mandatory in nearly every case. State explicitly which Azure regions you'll use.
• Incident notification mechanisms (timeline, contact, procedures).
• A service-exit plan: return, deletion, and a destruction attestation for the data at the end of the contract.

Canada Central hosting: a critical issue

In 2026 this has become a disqualifying criterion in most Québec public-sector RFPs. The implicit rule: the body's personal information and operational data must stay in Canada, ideally in Québec.

Microsoft has two Canadian regions: Canada Central (Toronto) and Canada East (Québec). For most Microsoft 365 workloads, it's Canada Central that hosts the tenant - including for Québec organizations. For Azure, you can pick the exact region.

Special case: some bodies (notably in healthcare) explicitly require Canada East. Check the specifications. Microsoft 365 doesn't offer a Canada East tenant option, which can create a compliance issue - a trade-off that's often acceptable with some documented back-and-forth, but one to anticipate.

Document it precisely in your response: "The Microsoft 365 tenant will be hosted in the Canada Central region. The Azure workloads deployed under this engagement will run in the Canada Central region, with geo-redundant backups to Canada East."

Typical scoring weights

Public-body selection committees generally use a two-stage grid: technical quality first, price second. The typical weighting in IT:

• Understanding of the need (10-15%): did you read the specifications, do you grasp what's at stake for the body?
• Expertise and experience (20-30%): references on similar engagements (size, sector, technology), résumés of the proposed resources, certifications.
• Methodological approach (15-25%): phases, deliverables, project management, change management, governance.
• Risk and quality management plan (10-15%): risks identified, mitigation measures, quality control.
• Price (20-30%): typically the lowest bid gets the top score, with a penalty formula for the gaps.
• Very often, the minimum quality threshold is 70% to move on to the price stage. A bid below 70% is eliminated, no matter the price.

Pitfalls that disqualify you on submission

Across the RFPs we've won and lost since 2018, here are the most common administrative disqualifications we've seen among competitors:

• An expired Revenu Québec attestation (valid for only 90 days).
• A bid bond in the wrong format (an uncertified cheque, an insufficient amount, a cheque made out to the wrong payee).
• A response not signed by an authorized person (a missing board resolution).
• A non-compliant format: public bodies often impose a specific response format (a Word template, numbered sections, a page limit). Any overage = elimination.
• A late submission, even by two minutes. The SEAO servers are strict about the official time.
• Undeclared subcontractors or an undisclosed conflict of interest.

Our approach to responding

At io4, we follow a proven method for every qualified RFP:

Day -15 - Go/no-go decision: a thorough review of the specifications, the response-effort-to-win-probability ratio, and alignment with our expertise (Microsoft 365 / Azure / security).

Day -12 - Internal scoping workshop: a senior architect plus a project lead decode the real need behind the requirements.

Day -10 to -3 - Drafting the response: methodological approach, proposed team, references, detailed plan.

Day -2 - Quality review by a senior who wasn't involved in the drafting: format compliance, consistency, and the relevance of the references.

Day -1 - Administrative validation: every attestation up to date, the bid bond prepared, the signatures obtained.

Submission day - SEAO upload no later than four hours before the deadline (to avoid any connection surprises).

This discipline lets us win a significant share of the RFPs we choose to respond to - precisely because we only respond to RFPs where we have genuinely differentiating expertise.