Understanding What Happens to Existing Scans When You Update Credentials

Updating a connector's credentials does not interrupt what AI Security is already doing. The existing connection keeps working until you save, and the activity already recorded is unaffected.

You update credentials when a key expires, when it has been rotated or revoked at the provider, or when a connector has stopped working and its status says the credentials are no longer valid. In every case the question is the same: what happens to the monitoring that is already running?

While you are editing

Nothing changes. Opening the panel and typing into it has no effect on the connector. The existing connection continues to work, and inspection continues, until you save.

If you decide not to go ahead, select Cancel. The connector is left exactly as it was.

Fields you leave blank

You do not have to re-enter every value. Leave an authentication field blank and the connector keeps the credential it already has. Only the fields you fill in are replaced.

This matters when a connector uses several values and only one has changed — a Microsoft Copilot connector, for example, holds a client ID, a client secret, and a tenant ID, and usually only the secret expires.

After you save

The connector starts using the new credentials from that point on. Activity recorded before the change stays where it is: your dashboard figures, your violation history, and the events behind them are all unaffected, because they describe activity that already happened rather than the connection that observed it.