connect-azure

Validating Azure credentials for compliance scanning requires connecting to the subscription to verify read access. This process scopes to the Azure environment, authenticates the account, and prepares the data for security scans.

Discovering Azure services for an ISO 27001 audit involves connecting to the subscription and inventorying active resources. This service discovery lists all deployed resources, ensuring the environment is fully scoped before initiating compliance checks.

Yes, Azure CLI is required to connect Shasta to your subscription. The CLI handles the authentication and connection process, allowing the tool to update configuration files with your tenant ID, subscription ID, and region.

Service discovery inventories Azure resources by authenticating against the target subscription and querying the environment. It lists active services and prepares the compliance-ready output needed to scope security workflows.

Connecting Shasta to Azure updates the shasta.config.json file with your specific subscription ID, tenant ID, and region. After validating credentials, it optionally initializes the local database to prepare for resource discovery.

Yes, you can initialize the local database when preparing an Azure compliance scan. After validating credentials and updating the configuration file, the process optionally initializes the database to support the compliance workflow.