Azure Connections

What this page is for

This page explains the purpose of saved Azure connections and how they fit into the review workflow.

When to use it

Read this when:

• you are deciding whether to save reusable access or use a one-off token
• you want to understand why the review modal behaves differently for saved connections
• you are setting up reusable access for repeated reviews

How saved connections work

A saved connection is a reusable Azure access path for the organization.

Hygiara uses it to:

• validate access before a review is queued
• discover accessible subscriptions
• make future reviews faster and more reliable
• optionally run scheduled continuous scans with a selected WAF rule set

When to use one

Use a saved connection when:

• the project will be reviewed more than once
• the same access should be reusable by the same or different operators
• you want a cleaner long-term workflow than pasting tokens every time

What to expect

Adding a connection does not start a review. It prepares the review flow so that later reviews can use that access path reliably without re-entering credentials each time.

If continuous scanning is enabled on the connection, the connection also stores the rule set used by the scheduled scan. You can choose all WAF rules or a custom rule set from the searchable selector.

Common mistakes

• Saving a connection when the work is genuinely a one-off
• Assuming the connection itself creates scan results unless continuous scanning is enabled

Next step

• Adding a connection
• Editing and validating a connection
• Access tokens