Exchange Settings for accounts with Multi Factor Authentication Enabled
- 28 Sep 2023
- 1 Minute to read
- Print
- PDF
Exchange Settings for accounts with Multi Factor Authentication Enabled
- Updated on 28 Sep 2023
- 1 Minute to read
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Scalefusion's Exchange Settings allows to configuration of exchange accounts which can be opened by native Mail applications on iOS devices.
In cases where a customer's Azure AD Exchange Account has Multi-Factor Authentication enabled, even on entering the correct password, the login might fail, and this is due to the absence of Multi-Factor Authentication during the login process. In order to solve this challenge, you need to use the payload below, which contains the necessary values to allow the native Mail app on the device to complete the Multi-Factor Authentication.
- Copy the contents directly from below and add it to Custom Settings in the Device Profile or click hereto download the file and import it in the Device Profile.Markup
DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>PayloadContentkey> <array> <dict> <key>EmailAddresskey> <string>XXXXXXXXX.onmicrosoft.comstring> <key>EnableCalendarskey> <true/> <key>EnableCalendarsUserOverridablekey> <true/> <key>EnableContactskey> <true/> <key>EnableContactsUserOverridablekey> <true/> <key>EnableMailkey> <true/> <key>EnableMailUserOverridablekey> <true/> <key>EnableNoteskey> <true/> <key>EnableNotesUserOverridablekey> <true/> <key>EnableReminderskey> <true/> <key>EnableRemindersUserOverridablekey> <true/> <key>Hostkey> <string>outlook.office365.comstring> <key>MailNumberOfPastDaysToSynckey> <integer>7integer> <key>OAuthkey> <true/> <key>OAuthSignInURLkey> <string>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXstring> <key>OAuthTokenRequestURLkey> <string>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXstring> <key>OverridePreviousPasswordkey> <false/> <key>PayloadDescriptionkey> <string>Configures an Exchange accountstring> <key>PayloadDisplayNamekey> <string>Exchange ActiveSyncstring> <key>PayloadIdentifierkey> <string>com.apple.eas.account.46977A5A-4BF4-4F78-A1E6-5E54A1CECDA4string> <key>PayloadTypekey> <string>com.apple.eas.accountstring> <key>PayloadUUIDkey> <string>46977A5A-4BF4-4F78-A1E6-5E54A1CECDA4string> <key>PayloadVersionkey> <integer>1integer> <key>PreventMovekey> <true/> <key>SMIMEEnabledkey> <false/> <key>SMIMEEncryptionEnabledkey> <false/> <key>SMIMESigningEnabledkey> <false/> <key>SSLkey> <false/> <key>UserNamekey> <string>XXXXXXXXX.onmicrosoft.comstring> <key>disableMailRecentsSyncingkey> <true/> dict> array> <key>PayloadDisplayNamekey> <string>Untitledstring> <key>PayloadIdentifierkey> <string>FVFW9RNXJ1WK.6CAA984D-3E8C-406B-BBC0-B7C743ABCF4Bstring> <key>PayloadRemovalDisallowedkey> <false/> <key>PayloadTypekey> <string>Configurationstring> <key>PayloadUUIDkey> <string>E6AE6596-D811-49EE-80D9-0D0336A7B754string> <key>PayloadVersionkey> <integer>1integer> dict> plist>
- In the above payload, please replace the following:
- Enter the email address of the Azure AD Admin.Markup
<key>EmailAddresskey> <string>XXXXXXXXX.onmicrosoft.comstring>
- The 2 keys, OAuthSignInURL & OAuthTokenRequestURL, have to be edited to match your Azure AD Accounts Tenant ID.Markup
<key>OAuthSignInURLkey> <string>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXstring> <key>OAuthTokenRequestURLkey> <string>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXstring>
- Enter the email address of the Azure AD Admin.Markup
<key>UserNamekey> <string>XXXXXXXXX.onmicrosoft.comstring>
- Enter the email address of the Azure AD Admin.
- Follow our guide on how to add the Custom Payload in the Device Profile & deploy it to devices.
Notes:
1. The Payload and its contents are sourced from various albeit authenticated Apple Developer communities and forums.
2. Please validate them on a test machine before deploying them on all your managed devices.
3. Scalefusion has tested these Payloads, however, Scalefusion will not be responsible for any loss of data or system malfunction that may arise due to the incorrect usage of these payloads.
2. Please validate them on a test machine before deploying them on all your managed devices.
3. Scalefusion has tested these Payloads, however, Scalefusion will not be responsible for any loss of data or system malfunction that may arise due to the incorrect usage of these payloads.
If you need additional help or guidance, please don't hesitate to reach out to our Support team. You can contact them through our live web chat or by sending an email to support@scalefusion.com
Was this article helpful?