EXPLORE THE DESIGN PARTNER BETA →
See what is available today, who the program is for, and how participation works.

VIEW THE PRODUCT ROADMAP →
See how TPZ moves from current read-only investigation to the Design Partner Beta, evidence-gated next steps, and longer-term cross-system direction.

READ OUR RESEARCH & WHITEPAPERS →
Explore TPZ research, technical writing, and selected public architecture material.

Questions about TPZ and the Design Partner Beta

CURRENT

  • TPZ brings supported Microsoft Entra identity and access context together for investigation and analysis. Teams can review users, directory roles, MFA registration, observed sign-in activity, Conditional Access policies, applications, service principals, and supported identity risk signals in one place. TPZ can also surface evidence-backed conditions that may deserve review.

  • No. TPZ’s Microsoft Entra access is read-only today. TPZ does not make changes to a customer’s Entra environment. Customer-authorized action is being validated as part of the Design Partner Beta.

  • When configured for live access, TPZ can read supported Microsoft Entra user, directory-role, MFA-registration, sign-in, policy, application, service-principal, and identity-risk information. Availability depends on configuration, permissions, licensing, API availability, and current coverage limits. TPZ does not make changes to your Entra environment today.

DESIGN PARTNER BETA

  • The Design Partner Beta is designed to prove one governed Microsoft Entra workflow end to end. Starting from a real identity or access finding, a designated customer participant explicitly authorizes the action. TPZ is designed to carry out the supported disable or deactivate user action, read the resulting state back from Microsoft Entra, verify the outcome, retain evidence, and support governed recovery.

  • The Design Partner Beta is a focused 12-week program with no cost to participate. The cohort is limited to up to five Design Partners.

  • The Design Partner Beta is intended for organizations that use Microsoft Entra, have a real identity or access problem worth working through, can identify an internal champion, can involve the administrators needed for setup and validation, and can participate in regular working sessions with TPZ. Best fit today is a Microsoft-heavy Financial Services or FinTech organization where one person or a small team carries broad cybersecurity responsibility and is willing to progress toward a customer-authorized remediation workflow.

SECURITY

  • TPZ’s current Microsoft Entra integration uses application permissions to retrieve supported identity and access context for investigation and analysis. Microsoft Entra access is read-only today.

  • Visit the Security page for TPZ’s current Microsoft Entra permissions, data categories, storage and retention information, credential handling, and the customer-authorization, read-back verification, retained-evidence, and governed-recovery model being validated in the Design Partner Beta.

PARTICIPATION

  • Design Partners provide access to the agreed Microsoft Entra environment, an internal champion, the administrators needed for setup and validation, regular participation in working sessions, and practical feedback on the findings and workflows being tested.

  • No. The Design Partner Beta begins from a read-only starting point. Any production action is condition-gated and requires the necessary technical, security, permission, and explicit customer-authorization controls before it can be evaluated. The customer remains the decision-maker.

INTEGRATIONS

  • TPZ’s current product focus is Microsoft Entra. During the Design Partner Beta, TPZ may evaluate additional relevant systems with each partner where they support the customer problem and create useful, reusable product learning.

  • No. Additional systems are selected with each Design Partner based on customer value, technical fit, reuse across customers, and what TPZ needs to learn. Specific vendors are not committed in advance.

COMMERICAL TRANSITION

  • The Design Partner Beta and any paid continuation are separate. If TPZ solves a meaningful problem and there is a fit on both sides, TPZ and the Design Partner can discuss the scope, pricing, and terms of a paid continuation. Participation in the Beta does not create an obligation to continue.

  • No. TPZ reviews each application individually based on fit, environment, participation readiness, and what the team can meaningfully validate together. Submitting an application does not guarantee acceptance into the Design Partner Beta.

FUTURE DIRECTION

  • TPZ’s longer-term direction is a cross-system security control plane that coordinates evidence, decisions, customer-authorized actions, verification, and retained proof across the systems organizations already use. Expansion beyond Microsoft Entra would depend on customer evidence, technical feasibility, and what TPZ learns through the Design Partner Beta. This is future direction, not current capability or a committed delivery schedule.

  • TPZ’s long-range direction may include more automation where the rules, authority, safety boundaries, verification, and recovery mechanisms are strong enough to support it. Any such automation would remain governed by customer-defined controls. Autonomous remediation is not a current product capability or a Design Partner Beta claim.