> ## Documentation Index
> Fetch the complete documentation index at: https://help.dsalta.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Offboarded users should not have active access

> Checks that offboarded users no longer have active Entra ID access.

Checks that offboarded users no longer have active Entra ID access.

## About

When you connect Entra (Office 365) to DSALTA, the platform syncs your users and groups using read-only access to Microsoft Graph. DSALTA identifies offboarded users — disabled accounts, and members of an offboarded group if one is configured — and checks whether any of them still hold enterprise app role assignments. If an offboarded user retains active assignments, DSALTA activates this check.

## Why This Matters

When someone leaves and their access is not revoked, their credentials become an unmonitored door into your systems — a common cause of data theft and accidental damage. Offboarded users should not retain assignments that grant access to applications. Timely access removal on termination is explicitly required by SOC 2, ISO 27001, and GDPR.

## How to Fix

**Before you begin**

* Identify all offboarded employees by cross-referencing your HRMS (or the DSALTA People module) with active Entra ID accounts.
* Ensure you have **Global Administrator** (or equivalent) access to your Microsoft Entra ID tenant.

**Remove access for offboarded users**

1. In the **Microsoft Entra admin center**, disable the offboarded user's account or move it to your **Offboarded** group.
2. Remove the user's **enterprise application** assignments.
3. Revoke the user's active sessions so existing tokens can no longer be used.
4. To automate this going forward, connect your HRMS to DSALTA so that an "Offboarded" status automatically flags any lingering access.

Once no offboarded user has active app role assignments, DSALTA retrieves the change on the next sync and sets the check status to **Passing**.

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="How often does this check run?">
    This check runs automatically every 24 hours while the Entra (Office 365) integration is connected. You can also trigger a manual sync from **Integrations** in the sidebar.
  </Accordion>

  <Accordion title="What happens if it keeps failing?">
    A failing check appears in your **Data Library → Tests** dashboard. Work through the steps above; once the underlying configuration is fixed, the status updates automatically on the next sync.
  </Accordion>

  <Accordion title="Can I exclude this check?">
    Yes. If it does not apply to your environment, mark it as **Not Applicable** with a justification. The exclusion is documented for auditors.
  </Accordion>

  <Accordion title="Does DSALTA change my Office 365 configuration?">
    No. DSALTA uses **read-only access** and never modifies, creates, or deletes resources. All remediation is performed by your team directly in the Microsoft Entra admin center.
  </Accordion>
</AccordionGroup>