Azure Maps Subscription Key
Detects Azure Maps subscription key patterns. This pattern is based on a Microsoft Purview built-in sensitive information type. Users already running Purview may prefer to enable the built-in SIT directly, or use this version as a starting point for customisation.
- Type
- regex
- Engine
- universal
- Confidence
- high
- Confidence justification
- High confidence: structurally constrained 32-character pattern with Azure Maps context keywords reduces false positive rates significantly. Added context gating and exclusion rules improve precision and reduce incidental matches.
- Detection quality
- Partial
- Jurisdictions
- global
- Regulations
- Criminal Code Act 1995 (Cth)
- Frameworks
- CIS Controls, ISO 27001, NIST CSF, PCI-DSS, SOC 2
- Data categories
- credentials, security
- Scope
- specific
- Risk rating
- 10
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported
Pattern
(?i)(?:subscription-key|maps[._-]?key|atlas[._-]?key)\s*[:=]\s*"?[A-Za-z0-9_\-]{32}"?Corroborative evidence keywords
Azure Maps, maps, subscription-key, atlas.microsoft.com, map service, geolocation, routing, geocoding, api key, api_key, apikey, access key, access token, auth token, authorization, bearer, conn str, connection string, connectionstring, cookie (+45 more)
Proximity: 300 characters
Should match
subscription-key=AAAA0000BBBB1111CCCC2222DDDD3333— Azure Maps subscription key (32 chars)maps_key: "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdef"— Maps key with mixed charactersatlas_key="00000000000000000000000000000000"— Maps key with placeholder value
Should not match
subscription-key=short— Too short to be a valid Maps keymapsAccountName=my-maps-account— Account name, not a keytemplate example placeholder record identifier— Template/sample context should be excluded even when anchor words are present
Known false positives
- Azure Maps documentation and sample applications with placeholder subscription keys. Mitigation: Check for common placeholder patterns and documentation context.
- Other 32-character API keys from non-Maps services. Mitigation: Use Azure Maps specific keywords (atlas.microsoft.com) for differentiation.