tag:help.appveyor.com,2012-11-13:/discussions/problems/29455-vso-webhook-now-failing-403-forbiddenAppVeyor: Discussion 2021-07-10T21:03:42Ztag:help.appveyor.com,2012-11-13:Comment/491863582021-05-10T10:24:03Z2021-05-10T10:24:05ZVSO Webhook now failing 403 Forbidden<div><p>Hi</p>
<p>This morning our VSO webhook has started receiving a 403 from the <a href="https://ci.appveyor.com/api/vso/webhook?id=">https://ci.appveyor.com/api/vso/webhook?id=</a> endpoint. Nothing has changed on the VOS side and the webhook has been working for years before this.</p>
<p>Am I missing something obvious or has something changed?</p>
<p>Thanks</p>
<p>Ben</p></div>Ben tag:help.appveyor.com,2012-11-13:Comment/491863582021-05-10T10:42:02Z2021-05-10T10:42:04ZVSO Webhook now failing 403 Forbidden<div><p>I got it sorted out. I found the following AppVeyor email:</p>
<p>AppVeyor uses OAuth to access Azure DevOps resources. Azure DevOps removed obsolete authorization scopes from OAuth flow which broke the integration with AppVeyor. As a result some AppVeyor customers were unable to login with VSTS button or start new builds with VSTS repositories.<br>
We deployed a fix and the customers should be able to re-authorize Azure DevOps on either "New project" or "Account > Authorization" pages. Unfortunately, we were unable to keep original OAuth app registration and had to create a new one, because scopes of existing app registration cannot be updated.</p>
<p>Cheers</p>
<p>Ben</p></div>Ben tag:help.appveyor.com,2012-11-13:Comment/491863582021-05-10T15:17:19Z2021-05-10T15:17:19ZVSO Webhook now failing 403 Forbidden<div><p>Hi Ben,</p>
<p>Thanks for the update and sharing the solution here.</p></div>Feodor Fitsner