Provenance
observed · 7 Aug
Freshness
fresh
Dispute
none
Revision
sha256:0f9040b390d0…

Agent report card

Can an agent use Microsoft for Startups through Direct application?

Grade F: Only part of the applicable terms is machine-readable.

Microsoft / ended

Agent ReadinessFBlocked
Coverage
complete: 11/11
Freshness
fresh
Last tested
Evidence
observed: not disputed

Five-stage assessment

Where agent autonomy holds and where it breaks

First break: Evaluate

  1. Evaluate

    Limited

    Only part of the applicable terms is machine-readable.

    Pricing is visible but incomplete or conditional.

    An ARD declaration has not been established.

    An agent can discover the product and funnel from the tested public entrypoints.

    Eligibility can be decided from explicit public criteria.

    Evidence and actions

    ARD declaration unknown

    missing: unknown

    An ARD declaration has not been established.

    ard_declaration: Unknown

    Decidable eligibility

    supported: fresh

    Eligibility can be decided from explicit public criteria.

    The application guide publishes an explicit criteria set before application.

    decidable_eligibility: Ready: tested 7 Aug

    Method headless 1

    Machine discovery

    supported: fresh

    An agent can discover the product and funnel from the tested public entrypoints.

    The public product page exposes an indexable program description and a direct application question and action.

    machine_discovery: Ready: tested 7 Aug

    Method headless 1

    Readable pricing limited

    supported: fresh

    Pricing is visible but incomplete or conditional.

    The public pages disclose credits and the maximum benefit, but the exact initial amount and later tier depend on path and approval.

    readable_pricing: Limited: tested 7 Aug

    Method headless 1

    Structured terms limited

    supported: fresh

    Only part of the applicable terms is machine-readable.

    The public overview structures program flow and criteria, while the complete customer and supplemental terms are accepted later inside account setup.

    structured_terms: Limited: tested 7 Aug

    Method headless 1

    What would improve this stage

    • Publish complete applicable terms in a stable machine-readable document.
    • Publish complete pricing, conditions, and any no-charge status in a stable machine-readable form.

  2. Sign up

    Blocked

    A CAPTCHA blocks autonomous signup.

    Phone or SMS verification blocks autonomous signup.

    The required identity flow is not usable by an agent.

    Only part of the signup flow is machine-operable.

    A stable signup entrypoint is available.

    Evidence and actions

    CAPTCHA-free signup unavailable

    supported: fresh

    A CAPTCHA blocks autonomous signup.

    Microsoft explicitly requires a prove-you-are-human verification during Azure account setup.

    captcha_free: Blocked: tested 7 Aug

    Method headless 1

    Machine-operable signup limited

    supported: fresh

    Only part of the signup flow is machine-operable.

    The guide documents ordinary form controls, but the public entrypoint renders only an application shell before identity-bound steps and the flow contains human-only checks.

    machine_operable_form: Limited: tested 7 Aug

    Method headless 1

    Phone-free signup unavailable

    supported: fresh

    Phone or SMS verification blocks autonomous signup.

    The application guide requires an SMS verification code before the application can continue.

    phone_verification_free: Blocked: tested 7 Aug

    Method headless 1

    Stable signup entrypoint

    supported: fresh

    A stable signup entrypoint is available.

    The declared signup URL resolved and the application guide documents the stable route into it.

    stable_entrypoint: Ready: tested 7 Aug

    Method headless 1

    Supported identity flow unavailable

    supported: fresh

    The required identity flow is not usable by an agent.

    The required personal Microsoft account, email code, SMS code, and human verification do not form an agent-usable delegated identity path.

    supported_identity_flow: Blocked: tested 7 Aug

    Method headless 1

    What blocks agents

    • A CAPTCHA blocks autonomous signup.
    • Phone or SMS verification blocks autonomous signup.
    • The required identity flow is not usable by an agent.

    What would improve this stage

    • Provide a documented agent-safe verification path that does not require solving a CAPTCHA.
    • Offer a documented verification path that does not require a human-controlled phone or SMS code.
    • Provide scoped, revocable machine authorization and document every required human approval boundary.
    • Expose labelled, deterministic controls and documented validation without requiring hidden human interaction.

  3. Pay

    Limited

    Pricing is only partly explicit or depends on undisclosed inputs.

    Checkout is only partly machine-operable or requires human intervention.

    The available payment rail is usable only with additional human intervention.

    The tested funnel can complete without sales intervention.

    Evidence and actions

    Explicit price limited

    supported: fresh

    Pricing is only partly explicit or depends on undisclosed inputs.

    No-upfront-charge and later pay-as-you-go behavior are explicit, but the two current guides disagree on the starter-credit amount and the eventual usage price is workload-dependent.

    explicit_price: Limited: tested 7 Aug

    Method headless 1

    Machine-operable checkout limited

    supported: fresh

    Checkout is only partly machine-operable or requires human intervention.

    The documented checkout has ordinary card fields, but it follows human verification and entering payment details is outside the observed agent authority boundary.

    machine_operable_checkout: Limited: tested 7 Aug

    Method headless 1

    Sales-free purchase

    supported: fresh

    The tested funnel can complete without sales intervention.

    The direct no-code path proceeds to self-service account creation without a required sales contact.

    sales_intervention_free: Ready: tested 7 Aug

    Method headless 1

    Supported payment rail limited

    supported: fresh

    The available payment rail is usable only with additional human intervention.

    A card rail is documented, but it requires human-held card data and consent rather than a delegated agent payment rail.

    supported_payment_rail: Limited: tested 7 Aug

    Method headless 1

    What would improve this stage

    • Publish the exact price, currency, conditions, and any no-charge status before commitment.
    • Expose documented, labelled checkout controls or an agent-compatible commerce interface.
    • Document a supported payment rail, authorization boundary, receipts, and failure semantics.

  4. Provision

    Blocked

    Provisioning status is not machine-readable.

    Activation is partly automatic or requires an unbounded manual step.

    Credential delivery is incomplete or requires human intervention.

    The provisioning delay has a documented and observed bound.

    Evidence and actions

    Automatic activation limited

    supported: fresh

    Activation is partly automatic or requires an unbounded manual step.

    Starter credits become available after account creation, while expanded benefits still depend on review and some credit balances can lag.

    automatic_activation: Limited: tested 7 Aug

    Method headless 1

    Bounded provisioning delay

    supported: fresh

    The provisioning delay has a documented and observed bound.

    The documentation gives explicit bounds for both application review and delayed credit appearance.

    bounded_delay: Ready: tested 7 Aug

    Method headless 1

    Credential delivery limited

    supported: fresh

    Credential delivery is incomplete or requires human intervention.

    Usable Azure access follows account creation, but the credential and account path requires unsupported human identity, consent, and payment handling.

    credential_delivery: Limited: tested 7 Aug

    Method headless 1

    Machine-readable provisioning status unavailable

    supported: fresh

    Provisioning status is not machine-readable.

    The declared operations surface documents status only in the signed-in Azure Portal; no machine-readable status interface is declared or documented for this funnel.

    machine_readable_status: Blocked: tested 7 Aug

    Method headless 1

    What blocks agents

    • Provisioning status is not machine-readable.

    What would improve this stage

    • Expose deterministic provisioning progress, terminal states, errors, cancellation, and reconciliation where applicable.
    • Automate activation or publish the exact bounded approval step and status.
    • Provide secure, documented credential or delegated-access delivery.

  5. Operate

    Blocked

    No documented machine-operable interface is available.

    Authentication requires unsupported human handling or hidden state.

    Limits and errors are documented only partially.

    Recovery is available only for some failure modes or requires human intervention.

    An agent protocol interface has not been established.

    Evidence and actions

    Agent protocol interface unknown

    missing: unknown

    An agent protocol interface has not been established.

    agent_protocol_interface: Unknown

    API or tool access unavailable

    supported: fresh

    No documented machine-operable interface is available.

    The exact declared operations resource documents a human portal and supplies no API or agent-tool interface for program and credit operations.

    api_tool_access: Blocked: tested 7 Aug

    Method headless 1

    Delegated recovery limited

    supported: fresh

    Recovery is available only for some failure modes or requires human intervention.

    Program recovery has documented support coverage, but it requires a signed-in human portal request rather than preserving a delegated agent boundary.

    delegated_recovery: Limited: tested 7 Aug

    Method headless 1

    Documented limits and errors limited

    supported: fresh

    Limits and errors are documented only partially.

    Activation errors and timing are documented, but the declared operations surface does not publish complete machine-oriented limits, error codes, and retry behavior.

    documented_limits_errors: Limited: tested 7 Aug

    Method headless 1

    Usable authentication unavailable

    supported: fresh

    Authentication requires unsupported human handling or hidden state.

    The documented operations path requires interactive portal sign-in and does not establish delegated agent authentication for this funnel.

    usable_authentication: Blocked: tested 7 Aug

    Method headless 1

    What blocks agents

    • No documented machine-operable interface is available.
    • Authentication requires unsupported human handling or hidden state.

    What would improve this stage

    • Publish a stable API or tool interface with capability and lifecycle documentation.
    • Support documented delegated authentication with explicit scopes and recovery.
    • Document limits, structured errors, safe retry behavior, and idempotency semantics for agent operations.
    • Provide delegated credential rotation, revocation, retry, and recovery paths without requiring unrestricted human intervention.

What works

No stage is currently established as ready or not applicable.

What blocks agents

  • Evaluate: Only part of the applicable terms is machine-readable.
  • Sign up: A CAPTCHA blocks autonomous signup.
  • Pay: Pricing is only partly explicit or depends on undisclosed inputs.
  • Provision: Provisioning status is not machine-readable.
  • Operate: No documented machine-operable interface is available.

Improve the report

Correct it, rerun it, or improve the funnel

Every request carries the exact profile revision, projection, declaration, and Catalog release.

Report outdated evidenceRequest reassessmentClaim this vendorView the exact declaration
Method, policy, and immutable identifiers

Complete, fresh evidence for the core service lifecycle first applies hard stage severity, then grades the share of applicable evidenced signals that are constrained. Optional blocker probes affect the grade when established and remain visible as unknown when public evidence cannot establish them.

Any incomplete, contradictory, unsupported, or non-fresh required evidence produces an unrated profile. A failed Evaluate, Sign up, or Pay stage derives D; a failed Provision or Operate stage derives F; otherwise constrained-signal ratio derives A+ through C.

Profile ID
arp_01kzcw21j3j40nr2h28cbwrbdm
Revision
sha256:0f9040b390d07292f3dce57a182bbc9b44ecadf56b1697512c1792e03423f294
Projection
sha256:8551aa136ee8d6e9f59fef87b76e13fa36cff4649f93f7a39b8540e3b0ed264a
Policy
service-lifecycle-2026-08-08-calibrated: sha256:334e56852b5c38e178fcea839cfba680fb82dd96693842d933776baed21d63df
Base Catalog release
sha256:5082ec07047a2324648f569d234cc64342ce2707b2f3d77fde8fc06af517cee6