Microsoft Security Exposure Management

ServiceNow data connector in Microsoft Security Exposure Management

4 September 2026Doc update+4 / −2 lines

In brief

The page title was shortened, author metadata was added, and the ServiceNow navigation path changed from “System OAuth -> Application Registry” to “System OAuth > Application Registry.”

What Defender admins need to know

The updated path notation makes the setup instruction easier to follow; no administrator action is required.

Summaries are generated from the documentation change itself.

Documentation change

View full page diff

View on Microsoft Learn

The comparison below shows only the changed extract. Use the full-page view for complete context.

Create the OAuth client (Application Registry)

Go to: System OAuth -> Application Registry.
Select: Create an OAuth API endpoint for external clients.
Fill mandatory fields (Name, etc.). Leave Redirect URL and Login URL blank (not used for client credentials).
Ensure Public Client remains unchecked (must be a confidential client).

@@ -1,7 +1,9 @@ ----title: Integrate ServiceNow data connector in Microsoft Security Exposure Management+title: ServiceNow data connector in Microsoft Security Exposure Management description: Learn how to the ServiceNow data connector in Microsoft Security Exposure Management. ms.topic: overview+ms.author: dlanger+author: dlanger ms.date: 10/23/2025 --- @@ -42,7 +44,7 @@ Use OAuth 2.0 client credentials to avoid storing a long‑lived password and to  ### Create the OAuth client (Application Registry) -1. Go to: System OAuth -> Application Registry.+1. Go to: System OAuth > Application Registry. 1. Select: Create an OAuth API endpoint for external clients. 1. Fill mandatory fields (Name, etc.). Leave Redirect URL and Login URL blank (not used for client credentials). 1. Ensure Public Client remains unchecked (must be a confidential client).