Separate customer state
Each customer installation has its own service configuration, state, databases, secrets and private network.
Deployment & subscriptions
Your product mix.
Your deployment scope.
Start with a focused priority. Install one, two or all three products under separate signed subscriptions.
Build your offering
One, two or all three.
Your priorities decide.
Separate subscriptions let you begin with a focused need and add complementary products when the scope grows.
Choose the products you would like to explore.
Discuss this offeringDeployment principles
Clear customer boundaries.
The offering uses separate customer installations with product-specific services and operational responsibilities.
Separate subscriptions
Signed entitlements enable the products you purchase. Add complementary products as the deployment scope evolves.
Operator tenant registry
Operator tooling can register customers and manage deployment entitlements. Customer consoles do not expose the operator registry.
A shared workspace
Product navigation, subscription management and governed reconciliation connect the offering while native permissions remain enforced.
Defined authentication
Each product retains native authentication and authorization. The shared workspace is distinct from unified single sign-on.
Explicit assessment scope
Microsoft collection uses approved service permissions and selected Azure subscriptions. Security Scan keeps evidence in a dedicated database.
Scope the first deployment
Start with an outcome
you can validate.
Choose the operational priority
An identity lifecycle, privileged system or Microsoft security assessment.
Define the environment
Identity sources, target systems, gateway requirements and authorized cloud services.
Agree the success evidence
Provisioning outcomes, session records or verified assessment results.
Protect Identity Solutions
Plan the right product mix.
Bring an identity journey, a critical system or a Microsoft security question. We will help you scope a product demonstration.