A test user, a group, an app registration? Get off here: it is self-service, with no request and no cost. Plenty of people ride all the way to a lab for nothing.
Testing authentication, validating a group mapping, running a script under an application identity: none of this
requires a lab. Any employee can create users, groups and app registrations in Entra ID, with no cost, no
quota, no request and no e-mail.
Test accounts, validating a sign-in flow, test data for an application role.
None
Groups
Testing membership, role mapping, token claims, dynamic assignment.
None
App registrations
OAuth 2.0 / OIDC, service principal for a script or pipeline, testing consent and permissions.
None
These objects are part of Entra ID’s free features. A license becomes necessary for a user who needs to consume
a paid service (Microsoft 365, Entra ID P1/P2 features). A test account that only signs in doesn’t need one.
A forgotten app registration keeps its secrets and permissions indefinitely. A neglected lab disappears; a
neglected Entra ID object piles up. Cleaning up is the price of self-service.
Any employee can create Entra ID users, groups and app registrations: no cost, no quota, no prior request. No e-mail and no lab needed. What you create, however, remains your responsibility until it is deleted.
Not blockingInternal practice
Delete objects as soon as you are done
My responsibility
Test users, groups and app registrations must be deleted once the need is over. A forgotten app registration keeps its secrets and permissions: unlike a lab, nothing expires it automatically.
MandatoryInternal practice
Short-lived secrets and certificates
Recommendation
Give any app registration secret or certificate the shortest lifetime that covers the need, and prefer renewing over a far-off expiry. Never paste a secret into code or a ticket.
Not blockingInternal practice
Identifiable naming
Recommendation
A name should tell who created it and why without any detective work: for example test-{trigramme}-{objet} for a user or group, and an explicit test purpose for an app registration.
Create your object with a recognizable name: your trigram and the purpose of the test, for example
test-qro-login-b2c. An anonymous name becomes an orphaned object nobody will dare delete.
For an app registration, give the secret or certificate the shortest lifetime that covers the need.
Write down the deletion date. No reminder will reach you.
Once the need is over, delete the object and its secrets.
A need that involves resources (VM, AKS, database, network) is a lab:
create my lab. A need for a sharing space belongs in
SharePoint, also self-service. The three can be combined; they simply follow separate
processes.