Best Practice for Service Account with Azure DevOps Boards Spoke OAuth Integration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi everyone,
We are implementing a ServiceNow to Azure DevOps integration using the Microsoft Azure DevOps Boards Spoke and OAuth 2.0.
The integration is currently working successfully in our DEV instance. Our flow is:
Incident created in ServiceNow -> Create Work Item action -> Bug created in Azure DevOps
For testing, I configured the Azure DevOps OAuth credential and used Get OAuth Token while authenticated with my personal Microsoft/ADO account.
The integration works, but Azure DevOps shows my name in the Created By field. We do not want the production integration to depend on an individual developer account.
We are planning to use a dedicated service/integration account.
My questions are:
- Is a dedicated service account recommended for this integration?
- Can a service account be used with Get OAuth Token?
- Should we re-authorize the existing OAuth credential with the service account, or create a new credential?
- Should DEV and PROD use separate service accounts?
- Can an Entra ID service principal be used instead of a user-based service account?
- After changing the OAuth identity, should Azure DevOps show the service account as Created By?
Any guidance would be appreciated.
This version avoids special formatting that could cause problems with the Community editor.