App analysis · 17.10.2026
Microsoft Authenticator
com.azure.authenticator · version 6.2609.6214
In short
SDKs found: 4. Companies: 2, of which outside the EEA — 2. Sensitive permissions: 10 — all code inside the app, including embedded SDKs, can use them.
What is inside — embedded SDKs
- Firebase Cloud Messaging — Google LLC, United States outside EEA push notifications
- Google Analytics — Google LLC, United States outside EEA analytics
- Google Firebase Analytics — Google LLC, United States outside EEA analytics
- Microsoft App Center — Microsoft, United States outside EEA analytics / crash reporting
Sensitive permissions (10)
- background location —
android.permission.ACCESS_BACKGROUND_LOCATION - approximate location —
android.permission.ACCESS_COARSE_LOCATION - precise location —
android.permission.ACCESS_FINE_LOCATION - authenticate accounts —
android.permission.AUTHENTICATE_ACCOUNTS - camera —
android.permission.CAMERA - NFC: reading cards, documents and tags —
android.permission.NFC - biometrics (fingerprint, face) —
android.permission.USE_BIOMETRIC - access credentials —
android.permission.USE_CREDENTIALS - fingerprint —
android.permission.USE_FINGERPRINT - draw over other apps —
android.permission.SYSTEM_ALERT_WINDOW
All manifest permissions (32)
android.permission.ACCESS_BACKGROUND_LOCATIONandroid.permission.ACCESS_COARSE_LOCATIONandroid.permission.ACCESS_FINE_LOCATIONandroid.permission.ACCESS_NETWORK_STATEandroid.permission.AUTHENTICATE_ACCOUNTSandroid.permission.CAMERAandroid.permission.FOREGROUND_SERVICEandroid.permission.FOREGROUND_SERVICE_LOCATIONandroid.permission.INTERNETandroid.permission.KILL_BACKGROUND_PROCESSESandroid.permission.MANAGE_ACCOUNTSandroid.permission.NFCandroid.permission.POST_NOTIFICATIONSandroid.permission.RECEIVE_BOOT_COMPLETEDandroid.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONSandroid.permission.SYSTEM_ALERT_WINDOWandroid.permission.USE_BIOMETRICandroid.permission.USE_CREDENTIALSandroid.permission.USE_FINGERPRINTandroid.permission.VIBRATEandroid.permission.WAKE_LOCKandroid.permission.sec.ENTERPRISE_DEVICE_ADMINandroid.permission.sec.MDM_CERTIFICATEandroid.permission.sec.MDM_SECURITYcom.azure.authenticator.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSIONcom.azure.authenticator.knox.SUPPORT_PERMISSIONcom.google.android.c2dm.permission.RECEIVEcom.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICEcom.samsung.android.knox.permission.KNOX_CERTIFICATEcom.samsung.android.knox.permission.KNOX_CERT_PROVISIONINGcom.samsung.android.knox.permission.KNOX_ENTERPRISE_DEVICE_ADMINcom.samsung.android.knox.permission.KNOX_SECURITY
Limits of the analysis
The analysis shows code inside the app file, not data transfers: an SDK being present means a transfer is possible, not that it happens. The country is where the company owning the SDK is registered, not where its servers are. Some code may have been renamed at build time, so the SDK list is a lower bound.
The legal assessment is made by the competent supervisory authority.
Evidence
com.azure.authenticator · version 6.2609.6214 (code 202662143)2db449fcf803493919782168793313b051212884e6f29344a34a6048c665eec1eebd0f16e629af8b8381bfedfdd649605fe90f763f5cb7ba473eb9eef94d9af113c27d15ac2eThe same file (same SHA-256) with the same library version gives the same result — check it on the APK check page. Licence CC BY 4.0, source — gdpru.eu; report errors to contact@gdpru.eu.