Bearer token not supported with the SyncSolutionToTeams operation

[waldekmastykarz]

When trying to call the SyncSolutionToTeams operation with a bearer token, you get the following error:

{
  "odata.error": {
    "code": "10005",
    "message": {
      "lang": "en-US",
      "value": "Authentication method is not allowed."
    }
  }
}

If this is by-design, we should update the docs to make it explicit that only cookie-based auth is supported.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 97580aa9-d30e-fc44-e83f-ae11422e7aa6
• Version Independent ID: 83691fea-7fbc-1b87-7c3f-08152d28f136
• Content: Application Lifecycle Management (ALM) APIs
• Content Source: docs/apis/alm-api-for-spfx-add-ins.md
• Product: sharepoint
• GitHub Login: @spdevdocs
• Microsoft Alias: spdevdocs

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[debi-dkrem]

Has there been any resolution to this? I'm suddenly getting a similar error when trying to teamify a site:

Add-PnPTeamsTeam : {"odata.error":{"code":"10005","message":{"lang":"en-US","value":"Authentication method is not allowed."}}}

[gitbrent]

Has there been any resolution to this? I'm suddenly getting a similar error when trying to teamify a site:

Add-PnPTeamsTeam : {"odata.error":{"code":"10005","message":{"lang":"en-US","value":"Authentication method is not allowed."}}}

Looks like it's related to this issue.

[mohandivraniya]

I am facing the same error when running Add-PnPTeamsTeam command with user authentication.

PnP.PowerShell version - 1.5.0
User running command is global, SharePoint and Teams administrator
User has valid SharePoint license assigned
Register-PnPManagementShell command executed and admin consent for all the permissions are given

What am I missing here?

@gautamdsheth would you be able to shed some light on this issue sir?

[giuleon]

The bearer Token is clearly not supported for SyncSolutionToTeams, docs should be updated.

[github-actions]

Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.

If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.

We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.