> ## 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.

# At least one identity source should be connected

> Checks that Nebius IAM is connected and a tenant identity source is reachable.

Checks that Nebius IAM is connected and a tenant identity source is reachable.

## About

When you connect Nebius to DSALTA, the platform uses the service account's read-only IAM access to confirm the connection is valid and that the tenant profile resolves. DSALTA evaluates this control on every sync. Compliance requires continuous visibility into who has access to your cloud infrastructure, so this check verifies the connection stays healthy.

## Why This Matters

If the Nebius IAM connection breaks, DSALTA can no longer collect access evidence and your identity and access checks stop reflecting reality — leaving gaps in your monitoring. Continuous visibility into who can reach cloud infrastructure is expected by frameworks including SOC 2, ISO 27001:2022, NIST CSF, and CIS.

## How to Fix

**Before you begin**

* Ensure you have **tenant admin** rights in the Nebius Console.
* Confirm the service account used for the connection still exists and is in the tenant **admins** or **editors** group.

**Restore the Nebius connection**

1. In DSALTA, go to **Integrations** and open **Nebius**.
2. If the integration shows Disconnected, click **Reconnect**.
3. In the Nebius Console, confirm the service account still has the DSALTA public key uploaded as an **authorized key**, and that it remains in the admins/editors group.
4. Re-enter your **Tenant ID**, **Service account ID**, and **Public key ID** in the secure window if prompted, then connect.

Once Nebius IAM is connected and the tenant is reachable, 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 Nebius 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 connection is restored, 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 Nebius configuration?">
    No. DSALTA uses **read-only IAM access** and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Nebius.
  </Accordion>
</AccordionGroup>