aitooltracking.Help centerSearch documentationCtrl K
Getting started

Register an enterprise and its first owner

Create a workspace from your Microsoft Entra directory, enroll the first Windows agent, and search its activity.

On this page

Create your organization’s workspace#

An active Microsoft Entra Global Administrator registers the organization and becomes its first workspace owner. Have your Microsoft 365 work domain or Entra tenant ID ready. If a colleague already registered your organization, use its dashboard sign-in link.

Choose Create a workspace, enter your work domain or tenant ID, and continue with Microsoft. Setup requests delegated read access to your profile, enterprise application assignments, group memberships and Conditional Access policies. If this is your directory’s first sign-in to the application, you may need to finish the Entra setup below and return to registration.

Configure the dashboard in Microsoft Entra#

In Enterprise applications, find AI Tool Tracking — Web. Verify its application ID is d0ffefde-011b-4d9c-8e68-5eac401a8b6d. Configure these settings in the directory you want to register.

  • In the application’s properties, enable Assignment required. Assign separate security groups for dashboard members and administrators. Add the registering administrator directly to the administrator group.
  • In Conditional Access, target the dashboard app and all client types. Apply the built-in Multifactor authentication strength to the member group and Phishing-resistant MFA to the administrator group. Enable both policies.
  • Automatic setup checks for dedicated group and app scopes without exclusions or alternative grants. Once the assignments and policies are in effect, return to Create a workspace and continue with Microsoft.

Continue when the workspace is ready#

If you see Preparing your workspace, Microsoft verification has finished. The service retries the collector connection every five minutes. In the same browser, select Check workspace readiness. When ready, the button takes you to your organization’s Microsoft sign-in.

The status check is available for 30 minutes in that browser. If it expires, enter your work domain on Resume workspace setup and sign in. If setup remains pending, give support the reference shown on the preparation page.

Enroll the first Windows endpoint#

Sign in to your new workspace, open Agents & devices, and create an enrollment code for the authorized Windows endpoint. Follow the installation instructions shown there. Keep the code private.

Find the endpoint in Agents & devices and check when its last heartbeat arrived. Then test the browser extension on a supported AI site using a harmless sample. Check AI activity for the event, its destination and the reporting endpoint.

Find a reported document#

Open AI activity and enter all or part of a filename under Search filenames. Select Apply filter. The hosted pilot searches seven days of retained observations across your workspace, including later result pages. For example, type договор to find ДОГОВОР-2026.pdf. The search treats % and _ as ordinary filename characters. You can narrow it to a finding or open View activity from one endpoint first.

Each match shows the AI tool, reporting endpoint and latest matching request when available. Open the event to review the available transfer history. A file selection records a browser gesture. Check related requests for an attempted transfer and its outcome. A matched filename alone does not establish a successful provider upload. The current filename search reads reported document names. Document bodies and clipboard text are absent from historical metadata.

Review a sensitive paste#

With Windows browser pilot 0.2.5 or later, a paste into a supported ChatGPT, Claude or Kimi page can report an API key, access token, private key header, labeled password or labeled secret alongside PII findings. Open AI activity, choose a finding filter and open the Text pasted event to see the device, destination, time and match count.

Detection runs on the endpoint. The report contains categories and counts. The pasted text is discarded after inspection. A paste records a browser gesture. It cannot establish that the user submitted the prompt or that a credential was valid. Ordinary unlabeled passwords can look like normal text. Pasting into a password field is excluded.

Review Microsoft sign-in configuration#

In the staging tenant dashboard, an owner or administrator can open Tenant administration and select Review Microsoft sign-in configuration. The panel shows the directory, application and group IDs assigned to that workspace.

Select Show read-only PowerShell commands. Run the commands in a Microsoft Graph PowerShell session for this directory and enter the approved member and administrator policy IDs. The commands save a JSON file in your current directory. To prepare the same file manually, use one JSON object. Under organization, include the directory object with its id. Under enterpriseApp, include the service principal with id, appId, accountEnabled, appRoleAssignmentRequired, servicePrincipalType and appOwnerOrganizationId. In the enterprise application properties, set Assignment required to Yes and collect a fresh export. Use memberGroupObject and adminGroupObject for the two group objects with id and securityEnabled.

Use memberPolicy and adminPolicy for the complete Conditional Access policy objects. Under groupAssignments, include a value array containing both groups' enterprise application assignments, with resourceId, principalId and principalType. Retrieve every page needed to identify those assignments. The review needs only configuration records.

Select the JSON file in the panel. The browser checks the export locally and lists differences such as a report-only administrator policy or a missing group assignment. The result describes the supplied snapshot. Confirm its collection time and use a fresh sign-in plus Entra sign-in logs to verify actual MFA enforcement.

Confirm the directory and its owner#

The customer’s Entra administrator supplies the tenant directory ID, the first owner’s user object ID and the object IDs for the member and administrator sign-in groups. Check that the owner belongs to the administrator group in this directory.

Verify that the enterprise app and group assignments match the customer’s approved Conditional Access policies. Members require MFA. Administrators and owners require phishing-resistant MFA. Record the approval in your change system.

Create the workspace#

The designated platform administrator opens Platform administration, selects Register enterprise, and enters the organization name, the four Entra IDs and the approved change reference. Review the details and select Create workspace.

The service reserves the directory and prepares a separate endpoint collector. Setting up means the first owner is still waiting for access. Refresh to check progress. If setup stays pending, contact support with the change reference.

Find enterprises waiting for action#

In Platform administration, Enterprise service status counts all registered enterprises. Select a count to open the matching directory entries. Selecting a count clears the previous name search and starts on the first page. To narrow those results, enter an enterprise name or directory ID and choose Search enterprises.

Setup pending means the first owner is waiting for collector provisioning. Sign-in groups missing identifies active workspaces that have finished or do not use that setup workflow and need their Entra access mapping reviewed. Device intake stop pending means the workspace is suspended and the collector has yet to acknowledge the stop. Pending operations show the last attempt when one has been recorded. Refresh to see whether the scheduled retry has completed.

No active owner lists active workspaces with completed or legacy setup whose roster has no active owner. An active tenant administrator can still be present. Check the enterprise and Entra directory IDs against the original onboarding or ownership-transfer receipt before routing the case to the authorized recovery contact.

Hand sign-in to the first owner#

When the enterprise is active and its Organization sign-in link appears, share that link with the first owner. The owner signs in with the approved Microsoft account and opens Tenant administration to add colleagues.

If registration reports a conflict, search for the directory ID and review the original change. Repeating registration cannot replace an owner or change sign-in groups. Intune consent and endpoint deployment have separate setup steps.

Retain and review an endpoint original on staging#

Sign in to the staging workspace as its owner and open Evidence vault. Download Windows evidence agent 0.3.0, enroll it, and enable its AI Tool Tracking — Evidence vault extension in the managed browser. Select the endpoint, review the retention notice with the Windows user and choose Enable original capture. Refresh until the endpoint acknowledges the policy revision.

The initial capacity is 1,000 MB. Save capacity changes the limit for this endpoint on its next check-in. Capture and quota reductions remove the oldest originals first. Disable and remove originals takes effect when the agent reconnects. The limit counts encrypted originals and manifests. Database bookkeeping and temporary transactions use additional disk space.

Evidence files shows the filename, endpoint capture time, AI tool, byte count, SHA-256 and last reported availability. Select Signed receipt to save its provenance. Download original requires the online agent and saves the verified bytes with an additional .evidence suffix. Keep the receipt alongside the downloaded copy. A retained receipt identifies an original even after the agent evicts it.

The extension correlates a selected, dropped or pasted file with a successful HTTP transfer on a supported ChatGPT, Claude or Kimi browser page. Providers can upload through another origin, transform files, or omit a recognizable filename. Ambiguous, unsupported, offline and failed flows can leave gaps. Native desktop applications have separate coverage. Endpoint and collector timestamps identify their respective observations. A provider storage acknowledgment and verified employee identity require additional evidence.

Related guides

Something missing or unclear?Suggest an improvement

Search documentation

Search titles, article text, and individual sections.

↑ ↓ to navigate · Enter to openSearch runs in your browser