Code to CloudCode to Cloud

Partner Program Confirmations

The single record of every vendor/program credential Code to Cloud has actually confirmed — what it says, where it’s verified, and where to cite it.

“Preferred partner” status shows up in two places: procurement supplier lists (see the government & public sector play) and vendor partner directories like Microsoft’s. This page tracks the second kind — confirmed, verifiable partner statuses — so every proposal, capability statement, and bid pulls from one accurate source instead of someone’s memory of a screenshot.

Status

Microsoft AI Cloud Partner Program

Confirmed Sep 15, 2026

Authorized — Active

Code To Cloud Inc. is verified as a Reseller in Microsoft's AI Cloud Partner Program. Verification status: Authorized. Program status: Active. Public Business Profile published Sep 2026 (live in Marketplace within ~24 hours); CSP (Cloud Solution Provider) application submitted.

Company name

Code To Cloud Inc.

Legal address

Graham Block, West Entrance, 401 Coopers Blvd SW #311, Airdrie, AB, T4B 4J3, Canada

Primary contact

Kevin Evans — kevin.evans@codetocloud.io

Primary contact phone

587-893-6419

Security contact

Kevin Evans — kevin.evans@codetocloud.io, 587-893-6419

Registration number on file

784848020RC0001

Global Partner ID — support calls only, never share

6884569

Location Partner ID — use this one operationally

6884570 (CSP enrollment, incentives, Marketplace/Business Profile 'Default Partner ID')

Public Business Profile

Published Sep 2026 — Services/ISV, Canada, Default Partner ID 6884570. Live in Marketplace within ~24 hours.

CSP (Cloud Solution Provider) application

Submitted Sep 2026 — status pending. Almost certainly lands as Indirect Reseller (Direct Bill needs $500K–$1M trailing-12-month CSP revenue, out of reach at this scale).

Cite in: Capability statement, RFP/tender responses (government-procurement play, action #17), and any prospect-facing pitch where vendor-side credibility matters. Use the Location Partner ID (6884570), not Global, for anything operational — a Pax8/CSP application, incentive enrollment, or the public Business Profile.

Related play

BDC Advisory Services Consultant Network

Confirmed Jul 2026

Joined — Active

Kevin Evans, representing Code to Cloud, is in BDC's national Advisory Services network as the AI, cloud & cybersecurity advisor — a federal-Crown-vetted credential and a live SMB referral channel.

Cite in: Anywhere independent third-party vetting matters — capability statements, the AI Source List qualification criteria, and BDC-referred client conversations.

Related play

Cloudflare Partner Program

Not yet applied

Flagged in the government-procurement play as the other vendor-side credential worth having. Route through Cloudflare's conflict-of-interest disclosure process first — Kevin joins Cloudflare Jul 2026 as an employee, so this needs explicit sign-off, not a routine partner application.

Cite in: Same places as the Microsoft listing, once cleared.

Related play

Next moves

Confirmed status is a credential to cite — these are the concrete follow-ups to turn it into something operational.

Confirm the CSP application lands as Indirect Reseller

Applied Sep 2026. Direct Bill CSP needs $500K–$1M in trailing-12-month CSP revenue (Microsoft's FY26 threshold) — out of reach at our scale — so this should come back as an Indirect Reseller enrollment. That alone still doesn't let us bill clients for M365: it needs pairing with an actual indirect-provider relationship.

Follow up with Pax8 once CSP status confirms

The outreach email to Pax8 is already drafted (Global Partner ID kept out of it; Location Partner ID 6884570 is the one to give them). Send once the CSP enrollment type is confirmed, so the conversation with Pax8 starts from the right footing. Not needed for clients who already own and pay for their own M365 tenant (e.g. Trinity Hills) — only if Code to Cloud wants to be the one selling/billing the licenses.

Reconcile the Partner Center contact email

'Profile info' still shows info@codetocloud.io as primary contact, while the top-level Legal business profile shows kevin.evans@codetocloud.io. info@ forwards but isn't actively monitored — align both to kevin.evans@codetocloud.io so CSP/Marketplace notifications don't land somewhere unread.

To verify — not blockers, just loose ends

Nothing here means the partner status is wrong — these are small inconsistencies inside Microsoft Partner Center’s own display worth a five-minute confirmation.

Registration number: RC0001 vs RT0001

Microsoft Partner Center shows registration number 784848020RC0001. The GST/HST account on file in org.ts is 784848020RT0001. Same business number (784848020), different CRA program-account suffix — RT is the GST/HST program, RC is typically payroll or another program account. Likely both correct and simply different accounts under the one BN, but worth a one-time confirmation with Microsoft support that RC0001 is what they intended to record, not a data-entry slip.

Contact email inconsistency inside Partner Center

The account-level 'Legal business profile' lists the primary and security contact as kevin.evans@codetocloud.io, but the 'Profile info' section further down lists the primary contact as info@codetocloud.io. info@ is a SharedMailbox that forwards to kevin.evans@ — not actively monitored as an inbox — so partner-program notifications should be confirmed to land somewhere read. Worth aligning both to kevin.evans@codetocloud.io inside Partner Center.