Confirm eligibility today by publishing your partner profile and submitting three client references. This actionable step unlocks the certification track and starts a clear, measurable path to benefits.
Publish your company page within 24 hours to appear in the partner directory, making it easy for a user to discover your capabilities. Your page lists the exact products, integrations, and the published performance metrics that demonstrate value to clients.
Keep your credentials current by automatically syncing certificates across jurisdictions and updating your profile whenever you release a new integration. Your status stays aligned with compliance standards and earns trust with some enterprise clients.
To improve clarity, we provide understandable criteria and a concise, step-by-step plan, with supporting guidance to help you map capabilities to the metrics, confirm requirements, and stay on track. This approach is actionable and designed to keep you on schedule, with explicit timelines and published targets.
Benefits include priority listing on the directory, co-marketing opportunities, and access to some major clients. By aligning with our metrics framework, you can measure impact, keep your clients informed, and improve satisfaction scores over time.
Next steps: go to the partner page, click Join, and follow the prompts to confirm your materials. Once submitted, you’ll receive a confirmation email and your status will update automatically within one business day.
Eligibility Criteria and Documentation Checklist
Verify your eligibility by aligning with these criteria and assembling the documents below. This time-sensitive process requires clear records that can be reviewed quickly and without ambiguity to the reviewer.
Eligible entities include software developers, studios, and creators with a registered business and an active account. A demonstrable product lineup with appswebsites and a track record of client reviews strengthens the submission. Teams that practice teamwork across regions and use a defined selector for roles increase alignment. For dutch markets, provide Dutch-language components alongside English versions.
Avoid vague materials. Prepare research-backed descriptions of offerings, a secure privacy policy, and evidence of compliance, including apostille where required for cross-border verification. The reviewer values intelligible documents that clearly explain how your version(s) integrate with Microsoft tools and how your team works together. Thats why this checklist helps you stay aligned.
Documentation checklist includes: corporate registration and legal entity information; tax ID; proof of address; authorization letter for signatories; a catalog of appswebsites with current versions and version histories; security and privacy policies; data processing agreements; evidence of reviews and customer feedback; access details for reviewer accounts or sandbox; translations in English and Dutch where applicable; apostille certificates where required; and submission-ready formats (PDF preferred).
Submission steps: use the partner portal to upload the files; ensure documents are signed and sealed as required; provide a concise executive summary highlighting outcomes, regions, and accepted formats; specify how the product portfolio supports microsoft integrations and how teams collaborate (teamwork). You will receive notifications about acceptance or requests for clarifications, plus a version-tracked record of the review (versions) and any updates (research) requested. This approach keeps the process clear for creators, reviewers, and account teams alike.
Application Submission: Steps and Typical Timelines
Submit a complete package in the initial submission window via the Partner Portal to minimize back-and-forth. the gordillo solutions team recommends a native, guided flow for the user, and you can start here to align identity, terms, and jurisdictions.
Prepare materials: company profile, identity documents for key contacts, updated offerings, customer reviews, workloads estimates, and supporting documents. This helps keep data consistent across all jurisdictions and ensures both customers and partners see the same picture.
Pack the submission: include terms, identify target jurisdictions, safeguard data with a dedicated layer, and ensure the window remains valid. Prepare to demonstrate how workloads will scale across native environments and how you protect customer data.
Submit via the portal: attach files, confirm fields, and use the Submit action; the system validates identity fields and routes to reviews.
Reviews and timelines: the review process breaks into two tracks–offerings alignment and compliance checks. The initial screening typically takes 5-7 business days, while compliance verification runs 10-15 days depending on document quality. If the reviewer requests additional information, respond within 3-5 days to keep the window on track.
Outcome and onboarding: you receive one of three outcomes–approval, request for more details, or decline. In all cases, you’ll get updated notifications here in the portal. approval triggers onboarding steps, kickoff scheduling, and access to dedicated resources from both teams to support a smooth transition.
Best practices: keep materials updated and aligned with native offerings; use consistent identity information across layers of data; verify terms before each submission; monitor reviewer feedback through the portal, and respond promptly to protect timelines. Focus on target customers and their workloads, and treat every update as a chance to refine your solution and supporting materials.
| Step | Actions | Typical Timeline | Notes |
|---|---|---|---|
| 1. Gather Materials | Compile company profile, identity proofs for key contacts, updated offerings, reviews, workloads estimates, and supporting documents | 3–7 business days | Ensure identity for primary contacts; align with customers and jurisdictions |
| 2. Package & Submit | Include terms, identify target jurisdictions, highlight data protection measures, confirm window validity | 1–2 business days | Submit via portal; use native file formats; solely rely on portal for submission tracking |
| 3. Automated & Human Reviews | Automated checks pass; human reviews assess offerings and compliance | 5–15 business days | Respond to data requests within 3–5 days to avoid delays |
| 4. Decision | Outcome issued: approved, needs more info, or declined | 5–10 business days post-review | On approval, proceed to onboarding; schedule kickoff with support teams |
| 5. Onboarding & Support | Access resources, configure accounts, align terms, train teams | 5–7 business days | Monitor workloads and customer usage; update offerings as needed |
Certification Levels, Milestones, and Evidence You Must Provide
Follow a three-tier model: Core, Advanced, and Expert, and attach evidence at each milestone to validate compliance and enable quicker acceptance.
Level 1: Core Certification
- Documentation: a Standards checklist aligned to current industry standards; includes a platform readiness report and a processes map for core workflows.
- Policy translation: translate key policies and user guides into required languages; include QA notes from native translators and a translation method description.
- Platform and integration: provide a native deployment diagram, data flows, and how your platform connects to destination systems via the selector.
- Risk and controls: deliver risk assessment, access controls, incident response plan, and evidence of accepted security controls.
- Evidence sources: include a источник pointing to the internal knowledge base and the origin of policy data, which ensures traceability of all documents.
Level 2: Advanced Certification
- Security and compliance: present security controls matched to your specialization and accepted standards, including encryption, role-based access, audit trails, and test results.
- Performance and scalability: share load test results for the services you provide, with clear targets for response times, throughput, and availability; include a documented method for capacity planning.
- Migration and localization: provide a migration method for moving workloads to destination environments; pair localization efforts with native UI guidelines and translation consistency.
- Customer validation: supply 2+ customer references with contact details and a short case study showing impact on operations.
- Quality assurance: include ongoing monitoring dashboards, service-level indicators, and a quality score derived from validated checks, with clear источник and verification method.
Partner Benefits: Co-Marketing, Sales Resources, and Support
Publish a public, co-branded offer page with a shared go-to-market plan and a quarterly review. Create a version of the assets and a versioned asset pack that includes battle cards, product sheets, customer case studies, and ready-to-run demos, before you scale to pilots.
Co-Marketing accelerates pipeline: run joint campaigns, co-brand social posts, and host webinars with an agreed calendar. Provide a dedicated icon and badge for partners, a public partner directory entry, and a switching-proof attribution model that ties pipeline to both sides within the azure cloud environment.
Sales Resources include battle cards, customizable email templates, pricing guides, and code samples that integrate with common CRM scripts. Maintain a central repository with analysis dashboards, bases for campaigns, checklists, and a public repository link for applying teams. Ensure these assets are relevant to buyers and include a quick check before field use.
Support makes success tangible: assign a partner success manager, guarantee SLA-backed escalations, and offer joint support hours for customers. Use a shared ticketing workflow, implement proactive health checks for customers, and publish clear expectations states on response times and issue ownership. This structure helps onboarding and reduces risk for azure-based deployments.
Onboarding and governance cover choosing agencies, managing compliance, and regional coverage like québec. Define eligibility rules, required certifications, and a simple applying process with actionable steps and checklists. Offer practical guidance for businesses and companies to validate alignment, set targets, and measure impact with a quarterly analysis of partner-driven revenue and customer satisfaction.
Advisory Services: Scope, Scheduling, and Deliverables
Define the advisory scope first and lock the terms before scheduling. Create a simple, shared format for objectives, data inputs, and success criteria, and secure sign-off from the client. This avoids drift and accelerates approvals.
The scope includes discovery, data collection, and a global view on regulations and compliance. This specialization helps tailor services to some businesses while maintaining a unified process. It flags risk areas early and prioritizes actions across multiple client contexts and alia networks.
Set a clear cadence for scheduling reviews: kickoff, biweekly check-ins, and a final delivery. Use an updated calendar visible to all stakeholders and define milestones with due dates. A fixed schedule reduces delays and makes progress transparent, while flags alert when scope or resource changes occur.
Deliverables include a data dictionary, an actionable advisory report, a gap-analysis summary, an implementation plan, and a training brief. Each item uses a consistent format, lists owners and due dates, and includes acceptance criteria. The package can be awarded to the client as formal artifacts, with an executive summary and a concise, ongoing update path.
To measure impact, tie updates to concrete metrics: data quality improvements, time-to-action reductions, and compliance posture shifts. The process also confirms alignment with regulations and client terms, and it includes a post-implementation review to verify outcomes and refine the plan as needed.
