Azure AD user credentials
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.
A paired username and password related to *.onmicrosoft.com domain.
Plain-text password used in code snippets.
Plain-text password used in XML configuration.
Various username and password formats, for example:
Various password formats in code snippets, for example:
new X509Certificates2( ...
ConvertTo-SecureString -String ********...
password = "********"...
"password" : "********"...
Various password formats in XML, for example:
... <secret>********</secret> ... ... <password>********</password> ... ... <setting name="password" value="********" > ... ... <setting name="password">********</setting> ... ... <setting name="password"><value>********</value></setting> ...
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.
This SIT is designed to match the security information that's used as individual user passwords to authenticate against Azure Active Directory.
It uses several primary resources:
- Patterns of Plain-text username and password for Azure AD tenants.
- Patterns of Password context in code.
- Patterns of Password context in XML.
- Patterns of CredentialName, CredentialFeatures, AccountIdentityName, AccountIdentityValue, ResourceType, ResourceName.
- Patterns of mockup values, redactions, and placeholders.
- A dictionary of vocabulary.
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.