search

getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
39.34k stars 4.21k forks source link

Sentry Azure Dev ops integration will break on Sep. 30 #77570

Open sentaur-athena opened 2 months ago

sentaur-athena commented 2 months ago

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

Microsoft is disabling Sentry's integration for Azure Dev ops on Sep. 30 based on this email sent to customers:

You are receiving this email because you are listed as a top user of the following third-party Azure DevOps OAuth app. As part of the Secure First Initiative, we are locking down all first-party (1P) usage of Azure DevOps OAuth.

·       App Id: 81b764b5-6558-4435-807c-4191963da611
·       App Name: Sentry (v3)
·       App URL: https://sentry.io/
·       Your Usage (last 30 days): 385

Starting September 30, we will block all third-party apps from being able to access any first-party resources.

These third-party apps using Azure DevOps OAuth have not been signed off by our Microsoft Digital Software Licensing Service that approves and manages all Third Party Software use at Microsoft.

Stop using this app

If you are no longer using this app or do not remember authorizing this app, revoke its authorization immediately.

After September 30, all apps will be blocked when attempting to access Microsoft resources. No exceptions will be made.

Continue using this app

If you would like to continue using the named app, you are asked to:

1.       Some apps have been already been restricted and evicted from the Microsoft software suite. Confirm that your app is not in this list and meet all accepted software requirements before requesting approval.
2.       Complete a request for software approval.
3.       Reach out to the app developer and make sure they have set up an Entra app to authenticate to Azure DevOps APIs. Azure DevOps OAuth apps will no longer be accepted to access 1P resources and is on the path to deprecation for all users.

Looking at documentation this means we need to create a new application using Entra and migrate our customers to the new integration.

Expected Result

N/A

Actual Result

N/A

Product Area

Settings - Integrations

Link

No response

DSN

No response

Version

No response

sentaur-athena commented 2 months ago

Posting some update on this issue. We're building a new integration for ADO and plan to migrate all ADO orgs to the new integration before Sep 30.

Right now IT is helping us get a verified microsoft partner account and Raj is planning the work needed for migrating away from the old integration to new without losing sync capabilities.

sentaur-athena commented 2 months ago

We have a fix merging today behind a feature flag for testing. The idea is that the customers with ADO will go to settings -> integrations -> Azure and install again. This will in the background replace the deprecated integration with a new one and migrate everything including issues and webhooks to work with the new one.

We will merge today and internally testing today and Monday. We'll work with CSMs to get help from a customer testing next week as well. If everything goes as planned coming Wednesday/Thursday we roll out the new integration to everyone and send comms about it.

Our marketing team will send an email to everyone with Azure Dev Ops integration and will work with CSM to communicate next steps to sales led customer.

sentaur-athena commented 2 months ago

We sent email to all customers yesterday with how to re-new the integration. So far no issues except people cannot install with their personal microsoft account. The app is definitely set up to allow personal accounts so we're working with Microsoft to see what's blocking the users.

umair-me commented 1 month ago

Have been sent here from the support team to follow this thread as I am having issues with signing in using personal Microsoft account. Sentry Ticket (133610)

Image