Skip to content
Cloud infrastructure/devops

windows.net:graphrbac

GraphRbacManagementClient sandbox and mock API

The Graph RBAC Management Client Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
56
Collections
-
Event types
-
Start this simulation
example request
curl https://your-windows-graphrbac.slurry.io/123/applications \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.6.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 56.

  • GET/{tenantID}/applications
  • POST/{tenantID}/applications
  • GET/{tenantID}/applications/{applicationObjectId}
  • PATCH/{tenantID}/applications/{applicationObjectId}
  • DELETE/{tenantID}/applications/{applicationObjectId}
  • POST/{tenantID}/applications/{applicationObjectId}/$links/owners
  • DELETE/{tenantID}/applications/{applicationObjectId}/$links/owners/{ownerObjectId}
  • GET/{tenantID}/applications/{applicationObjectId}/keyCredentials
  • PATCH/{tenantID}/applications/{applicationObjectId}/keyCredentials
  • GET/{tenantID}/applications/{applicationObjectId}/owners
  • GET/{tenantID}/applications/{applicationObjectId}/passwordCredentials
  • PATCH/{tenantID}/applications/{applicationObjectId}/passwordCredentials