Azure Storage account access key as it appears inside a connection string: the literal AccountKey= then eighty-six base64 characters and the two padding characters that a sixty-four byte key always produces. Self-anchored on the keyword, so noise is nil, and a key quoted on its own without that keyword is missed, which is also how the Microsoft detector behaves. The first example is the published Azurite emulator key, a known non-secret. No collision.
Label: AZURE_STORAGE_KEY
\bAccountKey=[A-Za-z0-9+/]{86}==DefaultEndpointsProtocol=https;AccountName=devstoreaccount1;AccountKey=Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==; → AccountKey=Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==La chaine de connexion portait AccountKey=AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA== en clair. → AccountKey=AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==AccountName=devstoreaccount1AccountKey=AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==Tags: international, secrets, software-dev