Getting an error when trying to verify my Identity

Jacques Bolduc 0 Reputation points
2026-06-06T20:31:43.52+00:00

We ahve to renew the MCPP but I get do it since, for any given reason, it voided my existing one. Now when I click on Validate, I get this error message:

https://credentials.microsoft.com/verify/ovdf-failure

No access

Some users, entities, and locations are restricted from using certain Microsoft services. For this reason, leveraging anonymizing or location hiding technologies (such as VPN, virtual machine, Internet tracking blocking, etc.) when connecting to these services is not allowed. If you are using one of these technologies, you'll need to disable/change your settings to gain access.

If you believe you encountered this problem without one of those causes, please wait 24 hours and try again. If the issue persists, contact our support team and reference the below message code and transaction ID. We will engage a team of experts that will help verify your account.

Transaction ID:

Community Center | Not monitored
0 comments

1 answer

Sort by: Newest
Most helpful Newest Oldest

  1. AI answer

    2026-06-06T20:32:01.0266667+00:00

    The error indicates that Microsoft’s identity verification service is blocking the request based on how or from where the connection is being made, and that self-service options are limited. The only supported resolution path in this scenario is to eliminate possible risk signals on the connection side, then work with Microsoft support (specifically the Data Protection/identity verification teams) if the block persists.

    Actionable steps:

    1. Eliminate environmental causes called out in the error
      • Turn off any VPN, proxy, anonymizing service, or privacy/traffic-filtering tools (including browser extensions that block tracking) on the device used for verification.
      • Avoid virtual machines or remote desktops; use a physical device on a standard, residential or corporate network.
      • Try a different network: for example, switch from corporate Wi‑Fi to a home network, or from Wi‑Fi to a mobile hotspot, to avoid IP ranges that might have a bad reputation.
      • Use a supported, up‑to‑date browser in normal (non‑incognito) mode.
    2. Respect the built‑in time and attempt limits
      • Repeated attempts can trigger additional protection and extend the block. After making the changes above, wait at least 24 hours before trying again, as the message suggests.
      • When you retry, complete the verification flow promptly. Similar Microsoft verification flows can fail if the process is left idle too long or repeatedly retried in a short period.
    3. If the block persists after 24 hours
      • Open a new support ticket specifically for identity verification / Partner Center access, and clearly state:
        • That this is blocking renewal of the Microsoft Cloud Partner Program (MCPP).
        • The exact error text and that it is an “ovdf-failure / No access” message.
        • The transaction ID from the error page.
      • Ask for escalation to the Data Protection or identity verification team. Similar MFA/identity lockout issues (including bad reputation on phone numbers or being locked out of global admin accounts) are resolved only by those internal teams via support tickets, not via self-service.
    4. If identity verification is in “Challenged” or “Rejected” state in Partner Center
      • Ensure that identity verification in Partner Center is not already in a failed state:
        • Check the account’s verification states (Email ownership, Identity verification) in the Partner Center profile.
        • If identity verification is Challenged, follow the guidance to obtain and present verifiable credentials from a trusted ID verification vendor, ensuring that the personal details exactly match the government ID used.
      • If identity verification is Rejected with no Fix now option, the account is suspended and only Microsoft support can resolve it.
    5. Use verifiable credentials correctly when prompted
      • When the flow asks for verifiable credentials issued by an ID verification vendor, make sure:
        • The details in Microsoft Entra / Partner Center (name, DOB, etc.) match the government ID used to obtain the credential.
        • The credential is presented from a supported device (for example, via Microsoft Authenticator) without VPN or anonymizing tools.
    6. If previous ticket was closed without resolution
      • Open a new ticket and reference the previous ticket number.
      • Clearly state that this is preventing MCPP renewal and that the error persists after disabling VPN/proxies, changing networks, and waiting more than 24 hours.
      • Request that the case not be closed until the Data Protection / identity verification team has reviewed the transaction ID and confirmed the block is removed or provided a remediation path.

    Because this block is enforced by Microsoft’s risk and verification systems, final resolution requires support to review the transaction ID and clear or adjust the block once environmental causes have been ruled out.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.