check before: 2022-10-17
Product:
Azure Active Directory, Entra, Entra ID, Exchange, Microsoft 365 admin center, Outlook
Platform:
Android, Developer, iOS, Mac, mobile, Online, Web, World tenant
Status:
Launched
Change type:
Retirement
Details:
We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21).
You can always read the latest information about our plans to turn off Basic Authentication here.
Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place.
In the month of September, we detected the following usage:
Exchange ActiveSync: 89
POP: 0
IMAP: 0
Outlook Windows: 0
Outlook for Mac/Exchange Web Services: 0
Exchange Remote PowerShell: 0
Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy).
If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices.
To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications.
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
Created:
2022-10-15
updated:
2023-09-18
Task Type
XXXXXXX ... free basic plan only
Docu to Check
XXXXXXX ... free basic plan only
MS How does it affect me
XXXXXXX ... free basic plan only
MS Preperations
XXXXXXX ... free basic plan only
MS Urgency
XXXXXXX ... free basic plan only
MS workload name
XXXXXXX ... free basic plan only
linked item details
XXXXXXX ... free basic plan only
** AI generated content. This information is not reliable.
the free basic plan is required to see all details. Sign up here
change history
| Date | Property | old | new |
| 2023-09-18 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-09-18 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-09-14 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-09-13 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-09-08 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-09-07 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-08-24 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-08-23 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-08-17 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-08-16 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-08-08 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-08-07 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-08-02 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-08-02 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-08-02 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-08-01 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-07-28 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-07-27 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-07-26 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-07-26 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-07-20 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-07-19 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-07-05 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-07-04 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-07-01 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-06-30 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-06-14 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-06-13 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-06-09 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-06-08 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-06-06 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-06-05 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-06-02 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-06-01 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-05-25 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-05-24 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-05-18 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-05-17 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-05-11 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-05-10 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-05-06 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-05-05 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-05-02 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-05-01 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-04-25 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-04-24 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-04-19 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-04-19 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-04-19 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-04-18 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-04-03 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-04-03 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-30 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-29 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-28 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-24 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-22 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-22 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-21 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-17 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-16 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-13 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-11 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-11 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-10 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-09 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-09 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-08 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-07 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-07 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-06 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-06 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-04 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-03-01 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-28 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-25 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-23 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-23 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-22 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-22 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-20 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-20 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-18 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-18 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-12 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-11 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-10 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-10 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-09 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-09 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-08 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-07 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-07 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-06 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-05 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-05 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-04 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-03 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-03 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-02 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-01 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-02-01 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-29 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-28 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-27 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-26 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-25 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-25 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-24 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-23 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-23 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-21 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-21 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-20 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-20 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-19 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-19 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-18 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-17 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-17 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-16 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-15 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-14 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-14 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-12 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-12 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-11 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-10 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-10 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-10 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-09 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-06 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-06 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-06 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-03 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-03 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2023-01-01 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-12-31 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-12-30 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-12-30 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-12-29 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-12-28 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-12-28 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-12-27 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-12-27 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-12-24 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-12-24 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-12-20 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-12-18 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-12-18 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-12-17 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-12-17 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-12-16 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-12-15 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-11-16 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-11-14 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-11-12 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-11-11 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-11-10 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-11-09 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-11-07 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-11-04 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-11-04 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-11-02 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-11-01 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-10-31 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-10-28 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-10-26 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-10-25 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-10-25 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-10-24 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-10-23 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-10-21 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-10-20 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-10-19 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-10-16 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
| 2022-10-15 | MC Messages | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022.
We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
Last updated 4 months ago
