Azure DevOps Wiki Connector - "Given email address is invalid" for Graph Connector Federated Credential App

2026-09-02T05:01:54.5166667+00:00

I am configuring an Azure DevOps Wiki Connector using Federated Credentials by following the Microsoft Learn document "Deploy the Azure DevOps Wiki connector".

The Graph Connector Federated Credential App exists as an Enterprise Application in Microsoft Entra ID.
(Before reaching the step of adding the application to Azure DevOps Organization Settings > Users, I was able to complete all preceding steps described in the deployment guide without any issues. The connector deployment process, including the Microsoft Entra ID configuration and the creation of the Graph Connector Federated Credential App, completed successfully.)

However, when I try to add it in Azure DevOps Organization Settings > Users > Add users, I receive the following error:

Given email address '933838e2-bec1-440f-a634-9363c82e5b6d' is invalid

https://learn.microsoft.com/en-us/microsoft-365/copilot/connectors/azure-devops-wiki-deployment#grant-the-microsoft-entra-app-access-to-azure-devops-projects

I would like to know which value should be specified in the Users or Service Principals field for the Graph Connector Federated Credential App (Application Name, Application ID, Object ID, or another identifier).

Additionally, are there any prerequisites or permission settings required before this application can be added to Azure DevOps?

Any guidance would be greatly appreciated. Thank you.

Azure DevOps

Answer accepted by question author
Vinodh247-1375 44,556 Reputation points Volunteer Moderator
2026-09-02T15:49:19.61+00:00

The identifier you're using (933838e2-bec1-440f-a634-9363c82e5b6d) is the Application (client) ID documented for the Microsoft-published Graph Connector Federated Credential App used by the Azure DevOps Wiki Connector deployment process. According to the connector deployment guidance, this is the value that should be entered when granting the connector access to Azure DevOps projects. [learn.microsoft.com]

However, there is an important distinction between:

  • Application (client) ID -> 933838e2-bec1-440f-a634-9363c82e5b6d
  • Enterprise Application (Service Principal) Object ID -> tenant-specific GUID
  • App Registration Object ID -> different GUID again

The Azure DevOps Wiki Connector documentation refers to the Application ID, whereas general Azure DevOps service principal guidance commonly references the service principal identity (display name or service principal object). Because of this difference, the error message can be confusing.

What to Verify?

  1. Confirm that the Graph Connector Federated Credential App exists under Microsoft Entra ID > Enterprise Applications.
  2. Verify that its Application (client) ID is exactly : 933838e2-bec1-440f-a634-9363c82e5b6d
  3. Ensure the Enterprise Application has been provisioned in the same Entra tenant associated with the Azure DevOps organisation.
  4. In Azure DevOps Organisation Settings, confirm that Third-party application access via OAuth is enabled, as this is a documented prerequisite for the Wiki Connector deployment. [learn.microsoft.com]
  5. If entering the Application ID results in the "Given email address is invalid" message, try locating the service principal by its display name (Graph Connector Federated Credential App) or by its Enterprise Application Object ID. This helps determine whether Azure DevOps is failing to resolve the application using the documented Application ID format.
  6. Once added successfully, ensure the account has:
    • Basic access level
    • Access to the projects being indexed
    • Membership in Project Readers (or an equivalent read-only group)
    • Send email invitation unchecked [learn.microsoft.com]
    • Additional Observation:

One detail not covered in the existing responses is that the error itself originates from Azure DevOps treating the supplied value as a user identifier during validation. If the Enterprise Application is present in Entra ID but cannot be resolved from Azure DevOps using the documented Application ID, that usually indicates an identity resolution issue between Azure DevOps and the connected Entra tenant rather than an incorrect connector App ID.

Since Microsoft's connector documentation explicitly references the Application ID above, I would first validate that the Enterprise Application exists and is visible in the same tenant connected to Azure DevOps, then test resolution using the service principal display name and Enterprise Application Object ID before assuming the identifier itself is incorrect.

Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Oldest

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.