Azure SQL connection string

Tip

If you're not an E5 customer, you can try all the premium features in Microsoft Purview for free. Use the 90-day Purview solutions trial to explore how robust Purview capabilities can help your organization manage data security and compliance needs. Start now at the Microsoft Purview compliance portal trials hub. Learn details about signing up and trial terms.

This SIT is also included in the All credentials bundled SIT.

Format

Up to 20,000-character combination of letters, digits, and special characters.

or

A pair of username and password used in general authentication process.

Pattern

Any combination of up to 20,000 characters consisting of:

  • a-z (not case-sensitive)
  • 0-9
  • forward slashes (/)
  • or plus signs (+)
  • Up to 2
  • equal signs (=)

for example:

MIIKcQIBAzCCCi0GCSqGSIb3DQEHAaCCCh4EggoaMIIKFjCCBg8GCSqGSIb3DQEHAaCCBgAEggX8MIIF+DCCBfQGCyqGSIb3DQEM

or

Variant username and password formats, for example:

username=...;password=********;
user id=...;password=********;
uid=...;pwd=********;
DB_USER=...;DB_PASS=********;
Service Account=...;Password=********;

Credential example

server=server.database.windows.net;database=database;user=user;pwd=ZYXWVU_2;

Checksum

Yes

SITs that have checksums use a unique calculation to check if the information is valid. This means when the Checksum value is Yes, the service can make a positive detection based on the sensitive data alone. When the Checksum value is No additional (secondary) elements must also be detected for the service to make a positive detection.

Definition

This SIT is designed to match the security information that's used to connect to Azure SQL Databases.

It uses several primary resources:

  • Patterns of Base64 encoded string literal.
  • Patterns of Plain-text username and password.
  • Patterns of CredentialName, CredentialFeatures, AccountIdentityName, AccountIdentityValue, ResourceType, ResourceName.
  • Patterns of mockup values, redactions, and placeholders.

The patterns are designed to match actual credentials with reasonable confidence. The patterns don't match credentials formatted as examples. Mockup values, redacted values, and placeholders, like credential type or usage descriptions, in the position where an actual secret value should present won't be matched.

Keywords

Keyword_Base64EncodedStringLiteral:

  • MII

Keyword_LoginCredentials:

  • password
  • pw
  • DB_