Microsoft Entra Global Secure Access
FundamentalsNetskope Integration
In brief
The Netskope integration example now uses different values for the tenantId and userId fields.
What Entra admins need to know
No administrator action is required.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
"sessionId": "",
"sourceIp": "clipped",
"sourcePort": "00000",
"tenantId": "44445555-eeee-6666-ffff-7777aaaa8888aaaabbbb-0000-cccc-1111-dddd2222eeee",
"trafficType": "Internet",
"transactionId": "55556666-ffff-7777-aaaa-8888bbbb9999",
"transportProtocol": "TCP",
"userId": "66667777-aaaa-8888-bbbb-9999cccc0000ffffffff-eeee-dddd-cccc-bbbbbbbbbbb0",
"userPrincipalName": "[email protected]",
"vendorNames": "Netskope"
}
@@ -286,11 +286,11 @@ This sample shows an event triggered by an ATP policy with blocked content. Chec "sessionId": "", "sourceIp": "clipped", "sourcePort": "00000",- "tenantId": "44445555-eeee-6666-ffff-7777aaaa8888",+ "tenantId": "aaaabbbb-0000-cccc-1111-dddd2222eeee", "trafficType": "Internet", "transactionId": "55556666-ffff-7777-aaaa-8888bbbb9999", "transportProtocol": "TCP",- "userId": "66667777-aaaa-8888-bbbb-9999cccc0000",+ "userId": "ffffffff-eeee-dddd-cccc-bbbbbbbbbbb0", "userPrincipalName": "[email protected]", "vendorNames": "Netskope" }