Forum Discussion
Guest accounts returning no repo when integrating with Azure Repos through Postman
Hello, I have a scenario I would like some guidance, at the company where I work we use the free Postman.
Our project collaboration and organization tool is Azure Devops.
In our teams there are people from other companies who join our projects through Azure Devops, as a guest account.
With that, we observe that people who are not from the same organization as us, but who have access to our projects because they were invited, cannot connect to our Azure Repos through Postman, currently I have identified that only people who are not invited are who can connect and view our repositories that are in Azure Repos...
People who are guests in our organization have the Basic + TestPlan profile
Can you advise me on this behavior?
User belonging to organization:
1 Reply
Take this:
- Enable Third-Party App Access in Azure DevOps
Make sure your organization has this enabled:
- Go to Azure DevOps > Organization Settings > Policies
- Toggle “Third-party application access via OAuth” to ON
- Use Internal Accounts Instead of Guests
If possible, create internal Azure AD accounts for external collaborators. This avoids the guest-user token limitations and ensures full compatibility with Postman.
- Use Personal Access Tokens (PAT) Instead of OAuth
Postman can connect to Azure DevOps using a PAT:
- Generate a PAT from Azure DevOps > User Settings > Personal Access Tokens
- Use it in Postman as a Basic Auth header:
Authorization: Basic <Base64EncodedPAT>This bypasses the OAuth flow and works for most users, including guests—though some restrictions may still apply depending on your Azure AD setup.
