Android app directory · Communication
Microsoft documents a short list of managed configuration keys for Teams on Android. Two of them speed up sign-in on shared devices, one locks the app to company accounts, and three more control what notifications show but only work when an Intune app protection policy is present. This page explains each one and which can be sent from any EMM.
Nomidcom.microsoft.teams Common setups
Copy a setup into the managed configuration of a policy, then adjust the values. Each one uses only keys explained below.
Pre-fill the domain and use the number keypad for staff who sign in with a numeric employee ID. Both keys only work on enrolled shared and managed devices.
{
"domain_name": "example.com",
"enable_numeric_emp_id_keypad": true
}Allow just the named work account in Teams. Use your EMM's user-name variable if you want one policy for many people.
{
"com.microsoft.intune.mam.AllowedAccountUPNs": "user@example.com"
}For organizations already using Intune app protection: set Org data notifications to Block org data and switch on the three keys through a managed apps policy. Notifications then show a short generic line instead of the content.
{
"com.microsoft.teams.chat.notifications.IntuneMAMOnly": 1,
"com.microsoft.teams.channel.notifications.IntuneMAMOnly": 1,
"com.microsoft.teams.other.notifications.IntuneMAMOnly": 1
}Managed configuration
Key names and value types come from the vendor’s documentation. The explanations are written by Nomid.
| Key | Type | What it does | Example |
|---|---|---|---|
| Sign-in on shared and managed devices | |||
com.microsoft.intune.mam.AllowedAccountUPNs | User principal names, separated by semicolons | Allows only the listed work accounts in Teams and blocks personal ones. Microsoft lists Teams among the apps that read this key on Android, and it travels through the normal managed configuration channel. | user@example.com |
domain_name | Tenant domain, semicolon separated for several | Fills in the domain on the sign-in screen so people only type the first part of their address. Microsoft says it works on enrolled shared and managed devices. | example.com |
enable_numeric_emp_id_keypad | On or off | Opens the number keypad for sign-in when employee IDs are digits only. Without it the full keyboard appears. | true |
| Notification content (needs Intune app protection) | |||
com.microsoft.teams.chat.notifications.IntuneMAMOnly | Choice: 1 on, 0 off | Turns on the hide-details notification behavior for chat messages. It is read by the Intune app protection channel, so it has no effect from another EMM on its own. | 1 |
com.microsoft.teams.channel.notifications.IntuneMAMOnly | Choice: 1 on, 0 off | Same behavior for channel notifications. | 1 |
com.microsoft.teams.other.notifications.IntuneMAMOnly | Choice: 1 on, 0 off | Same behavior for all other Teams notifications, such as meeting reminders. | 1 |
Deploy with Nomid
Find it on Google Play from the policy’s apps list and choose how it is installed.
In the policy, set the app’s managed configuration with the keys and values from this page.
Devices in the policy receive Microsoft Teams and its configuration on their next sync.
Questions
com.microsoft.teams. Use it to find the app when you add it to a policy, or in an adb command.
The allowed accounts key, domain_name and enable_numeric_emp_id_keypad. Microsoft says the account restriction works with any UEM provider on enrolled devices. The three notification keys end in IntuneMAMOnly and depend on an Intune app protection policy.
Yes for the allowed accounts key: put more than one user principal name in the value and separate them with semicolons.
The device-channel keys need the phone to be enrolled with Android Enterprise and Teams to be installed from managed Google Play, which includes work profile devices.
Add the app to a Nomid policy, set its configuration and choose its permissions.
