AzureVCRBaseTest attempts to automatically obscure keys and other secrets in cassettes and replace subscription ids,
but it is required to verify cassettes don’t contain any sensitive information before submitting.

For long standing operations cassette can be modified to reduce test execution time (in case recorded cassette contains some responses with Retry-After headers or Azure SDK waits until resource is provisioned).

You can use tox to run all tests or instead you can use pytest and run only Azure tests (or only specific set of tests). Runing recorded tests still requires some authentication, it is possible to use fake data for authorization token and subscription id.