2: Keeping secrets secret

One thing that is important to realize when working with workflows is that you need to avoid putting sensitive information about Azure Synapse inside your workflows.

A good example of how somebody can accidentally expose sensitive information can be found in my post 'Keep your Azure Synapse secrets secret in GitHub'.

In reality, there are a various ways you can keep sensitive information secure when working with workflows within GitHub. Including the below methods:

1. Adding encrypted secrets to your repository.
2. Adding encrypted secrets at an organization level (depending on which GitHub product you are using)
3. Using a GitHub Action called get-keyvault-secrets to get secrets from the Azure Key Vault service.

Due to more companies requesting the use of Azure Key Vault options 3 may be more appealing to you.

For more information about the above you can read my post 'Keep your Azure Synapse secrets secret in GitHub' and adapt it for Azure SQL Database deployments.