ProtectionScopes.Compute.User
Allows the app to identify Purview data protection, compliance and governance policy scopes defined for an individual user.
In short
ProtectionScopes.Compute.User is available as both an application permission and a delegated permission in the Microsoft Graph API, grouped under the ProtectionScopes category. Allows the app to identify Purview data protection, compliance and governance policy scopes defined for an individual user. It grants read-only access to resources. Application permissions always require admin consent.
Permission Details
Compute Purview policies for an individual user
Allows the app to identify Purview data protection, compliance and governance policy scopes defined for an individual user.
fe696d63-5e1f-4515-8232-cccc316903c6
Compute Purview policies for an individual user
Allows the app to identify Purview data protection, compliance and governance policy scopes defined for an individual user.
4fc04d16-a9fc-4c5e-8da4-79b6c33638a4
Properties
Properties is shown from stable Microsoft Graph v1.0 metadata.
| Property | Type | Description |
|---|---|---|
id |
String |
The unique ID of the data security and governance stream. Inherited from entity. |
sensitivityLabels |
sensitivityLabel collection |
JSON Representation
JSON representation is shown from stable Microsoft Graph v1.0 metadata.
{
"@odata.type": "#microsoft.graph.dataSecurityAndGovernance",
"id": "String (identifier)"
}
Relationships
Relationships is shown from stable Microsoft Graph v1.0 metadata.
| Relationship | Type | Description |
|---|---|---|
sensitivityLabels |
sensitivityLabel collection |
Related sensitivityLabels data exposed by this resource. |
Graph Methods
Microsoft Graph v1.0 endpoints are mapped directly from refreshed Microsoft Learn permissions tables.
| Methods |
|---|
POST
/me/dataSecurityAndGovernance/protectionScopes/compute
|
POST
/users/{usersId}/dataSecurityAndGovernance/protectionScopes/compute
|
Microsoft Graph beta endpoints are mapped directly from refreshed Microsoft Learn permissions tables.
| Methods |
|---|
POST
/me/dataSecurityAndGovernance/protectionScopes/compute
|
POST
/users/{usersId}/dataSecurityAndGovernance/protectionScopes/compute
|
Microsoft Graph PowerShell v1.0 commands are not available from refreshed Microsoft Learn PowerShell snippets for this permission.
No deterministic PowerShell command map is available for this permission.
Browse PowerShell docsMicrosoft Graph PowerShell beta commands are not available from refreshed Microsoft Learn PowerShell snippets for this permission.
No deterministic PowerShell command map is available for this permission.
Browse PowerShell docsCode Examples
using Azure.Identity;
using Microsoft.Graph;
var scopes = new[] { "ProtectionScopes.Compute.User" };
var credential = new InteractiveBrowserCredential(
new InteractiveBrowserCredentialOptions
{
ClientId = "YOUR_CLIENT_ID",
TenantId = "YOUR_TENANT_ID",
RedirectUri = new Uri("http://localhost")
});
var graphClient = new GraphServiceClient(credential, scopes);
var response = await graphClient
.WithUrl("https://graph.microsoft.com/v1.0/me/dataSecurityAndGovernance/protectionScopes/compute")
.GetAsync();
import { Client } from "@microsoft/microsoft-graph-client";
import { InteractiveBrowserCredential } from "@azure/identity";
const credential = new InteractiveBrowserCredential({
clientId: "YOUR_CLIENT_ID",
tenantId: "YOUR_TENANT_ID",
redirectUri: "http://localhost"
});
const token = await credential.getToken(["ProtectionScopes.Compute.User"]);
const client = Client.init({
authProvider: (done) => done(null, token.token)
});
const response = await client.api("/me/dataSecurityAndGovernance/protectionScopes/compute").get();
Connect-MgGraph -Scopes "ProtectionScopes.Compute.User"
Invoke-MgGraphRequest -Method GET -Uri "https://graph.microsoft.com/v1.0/me/dataSecurityAndGovernance/protectionScopes/compute"
from azure.identity import InteractiveBrowserCredential
import requests
credential = InteractiveBrowserCredential(
client_id="YOUR_CLIENT_ID",
tenant_id="YOUR_TENANT_ID"
)
token = credential.get_token("ProtectionScopes.Compute.User")
response = requests.get(
"https://graph.microsoft.com/v1.0/me/dataSecurityAndGovernance/protectionScopes/compute",
headers={"Authorization": f"Bearer {token.token}"}
)
print(response.json())
App Registration
Navigate to Azure Portal
Go to App registrations in Microsoft Entra admin center
Add API Permission
Select your app → API permissions → Add a permission → Microsoft Graph
Select Permission Type
Choose Application permissions or delegated permissions and search for ProtectionScopes.Compute.User
Grant Admin Consent
Application permissions always require admin consent.
Frequently asked questions
What is the ProtectionScopes.Compute.User Microsoft Graph permission?
ProtectionScopes.Compute.User is available as both an application permission and a delegated permission in the Microsoft Graph API, grouped under the ProtectionScopes category. Allows the app to identify Purview data protection, compliance and governance policy scopes defined for an individual user. It grants read-only access to resources. Application permissions always require admin consent. It is mapped to the Microsoft Graph datasecurityandgovernance resource type. 4 documented Microsoft Graph REST methods require it.
Is ProtectionScopes.Compute.User an application or a delegated permission?
ProtectionScopes.Compute.User is available as both an application permission (app-only access, no signed-in user) and a delegated permission (access on behalf of a signed-in user).
Does ProtectionScopes.Compute.User require admin consent?
Application permissions always require admin consent.
What is the permission ID (GUID) for ProtectionScopes.Compute.User?
For ProtectionScopes.Compute.User, the application (app role) ID is fe696d63-5e1f-4515-8232-cccc316903c6, and the delegated (OAuth2 scope) ID is 4fc04d16-a9fc-4c5e-8da4-79b6c33638a4. These are the real Microsoft Graph identifiers and can be used directly in an app registration manifest.