techcommunity.microsoft.com
Open in
urlscan Pro
2a02:26f0:7100:1a9::207e
Public Scan
URL:
https://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authentication-and-exchange-online-september-2021-update/ba-p/2772210
Submission: On April 11 via api from IE — Scanned from DE
Submission: On April 11 via api from IE — Scanned from DE
Form analysis 2 forms found in the DOM
Name: form_3ba3feee409c27 — POST https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.searchformv32.form.form
<form enctype="multipart/form-data" class="lia-form lia-form-inline SearchForm" action="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.searchformv32.form.form" method="post" id="form_3ba3feee409c27" name="form_3ba3feee409c27">
<div class="t-invisible"><input value="blog-id/Exchange/article-id/31221" name="t:ac" type="hidden"><input value="search/contributions/page" name="t:cp" type="hidden"><input
value="9noadVNP7YDBR8Rki66MDkkGePc1gJZxTHXJtxyGXvGmy4VKXpBmVnuodFupeXoWT1jiy-0gV1IzgZdHIZ5F6v0931uSS9Q80ggRwNXGAna2hSnOjb57M_0lvIgDIjdxdeoy3G7s1FjL9_lrThfyFUdEZsZAk8jXBgFxzc3ieb14SmyC1oV_0BxXvjHKVZncMFJ38IdEWwIlVclnjpdNUX-Y0o1C67Rvjjwa4Mk2S3uuKe619Ry34VbZ6-tP6RcjaTwqhfLVTQZQkReXokkCKmhokJIiI8Ov0dbBN7RzBffZgR7YfjDa4BZT4glwZRXoRzfaQH1sJi1rbQmjJFKTo42oREdeHHtqVfaNZZGVnsfdzzuOjJEuNKiVXor1fEca7KnZXb-DSiKi6C8hrMZwBZEdqaHaqgq1pXYmbbnvmaRWtiP0lfJuOfStPPRioIL-1jhnnq9unnFYN79TeZIcStRXZG-pHg7-kzW8wfkIdIcg7FdhcHGKatsvaYWhQm2bhyJtteDuu2alB8ZyfGwXLP0LHJfm1Zln_hihjWk3eu6nkFGNTQatZaZGz8YrdRlJ-qUeAYdEGpYGgNQnzem7UWz2mH7lJTRZq0STWKbJpVGp1VS_OzVhCgQyvNFtXH-h_ZF8ZcpO3XstGuZyS4kJU6oOpeEz_JndejaftdQsurxlQycyD8GPOo6kuhHukZQp122navaSWPvWVW2faZ2B-BczDJsqZKS2TFeyUWariVgaArwNqn1YDHZkjhGNmrPraak7ZjqtpOjEzO8uf5SBO5EUSg0sU6uI4URuLm0s-6y4v2ZjYGpU_GTv8QZShTqkH81M-tPkaJEn8MvM44K7WuooKf6ETbT_eGqYLjUJdyHqYoKBwb5W3x2jRCj-fyH3T8317yVFPyuvPDfay0iFi6Usyab_djy173Kd925jIULPQVTV2Ac4CGx0iQ8y1hdbAeypAK1iF5YXnUXbnhVJaXPwHVRpekb6HPPZXe9y25-HI4zIvC1WwBBvZ8WQHkrWueRt89cgMml2iAup0sgNRpYOu-LYFYoe7v1-CdjQUn-uoBJDLI14gUjhuiLtVwjqo51FVW7lFpXjoEq8wF7QpSWNg2gcE55gJYyYyZX6znAXFTvRg7lKAOUNsn2DjszZESoa1kyJZtyPL20_zNlgt9t9Xk4G7hl6rmTi4n5oUoptmJ-ZI0iopgsLnwwwcpTNlHnVmshspivxF13znKkaxJjYG6JUNJsuR8HGc8C5fLbjvA78NtKyhsYYGXRogKKgAL3I24L6k5ioWhZiOB2tjQ.."
name="lia-form-context" type="hidden"><input value="BlogArticlePage:blog-id/Exchange/article-id/31221:searchformv32.form:" name="liaFormContentKey" type="hidden"><input
value="yDZKQFNI0U/sd9X4pbUemqvQQZw=:H4sIAAAAAAAAALWSzUrDQBSFr4Wuigiib6DbiajdqAhFUISqweBaZibTNJpk4sxNEzc+ik8gvkQX7nwHH8CtKxfmzxJbwaTUVZhzw/nOmblP79COD+FAC6r40OAyQOWyCF0ZaMOkjtgrJgOp/NHONtER810sP9nfIkGtoCuVQ2hI+VAQpKHQqO67hEslPJcRRrUgPZaKlOOxKzx7wxIYhZtX487b+stnC5b60MnZ0junvkBY7d/QETU8GjiGlUYKnP0kRFguwEcFeAHBe02Dm0pyobWV+Wid0sbP9u7g4/G1BZCE8QWc1U3kpzapWoqZ+S+SvoMHgPQ+ypGVj/IoC2dlqHZ8CWZdV7xljUqszZa43voPYNHkFE7qGkdaqKrl1Pm7wEqmV59gcYjGkQOJP25h6jyJnOlzRv4DUURusIWhknbEsWo5K002vhzNufG1WHmDLwdzh8gDBQAA"
name="t:formdata" type="hidden"></div>
<div class="lia-inline-ajax-feedback">
<div class="AjaxFeedback" id="feedback_3ba3feee409c27"></div>
</div>
<input value="OokQd2R6oYogtlmOtACvlehKrJhbi7czuh_JIV5X5jI." name="lia-action-token" type="hidden">
<input value="form_3ba3feee409c27" id="form_UIDform_3ba3feee409c27" name="form_UID" type="hidden">
<input value="" id="form_instance_keyform_3ba3feee409c27" name="form_instance_key" type="hidden">
<span class="lia-search-input-wrapper">
<span class="lia-search-input-field">
<span class="lia-button-wrapper lia-button-wrapper-secondary lia-button-wrapper-searchForm-action"><input value="searchForm" name="submitContextX" type="hidden"><input class="lia-button lia-button-secondary lia-button-searchForm-action"
value="Search" id="submitContext_3ba3feee409c27" name="submitContext" type="submit"></span>
<input placeholder="Search the community" aria-label="Search" title="Search" class="lia-form-type-text lia-autocomplete-input search-input lia-search-input-message" value="" id="messageSearchField_3ba3feee409c27_0" name="messageSearchField"
type="text" aria-autocomplete="both" autocomplete="off">
<div class="lia-autocomplete-container" style="display: none; position: absolute;">
<div class="lia-autocomplete-header">Enter a search word</div>
<div class="lia-autocomplete-content">
<ul></ul>
</div>
<div class="lia-autocomplete-footer">
<a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="yn9zfHX5D3ekDjVeW_zlgRGBbNM33yhe_6U46VDEL6Y." rel="nofollow" id="disableAutoComplete_3ba3feee6e4ad0" href="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/Exchange/article-id/31221&t:cp=action/contributions/searchactions">Turn off suggestions</a>
</div>
</div>
<input placeholder="Search the community" aria-label="Search" title="Search" class="lia-form-type-text lia-autocomplete-input search-input lia-search-input-tkb-article lia-js-hidden" value="" id="messageSearchField_3ba3feee409c27_1"
name="messageSearchField_0" type="text" aria-autocomplete="both" autocomplete="off">
<div class="lia-autocomplete-container" style="display: none; position: absolute;">
<div class="lia-autocomplete-header">Enter a search word</div>
<div class="lia-autocomplete-content">
<ul></ul>
</div>
<div class="lia-autocomplete-footer">
<a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="u-Y6GYM8trq5x5i9rPDhlMQkSuUGnlSOC2Pa12Yd8XA." rel="nofollow" id="disableAutoComplete_3ba3feeee17bcf" href="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/Exchange/article-id/31221&t:cp=action/contributions/searchactions">Turn off suggestions</a>
</div>
</div>
<input placeholder="Search all content" ng-non-bindable="" title="Enter a user name or rank" class="lia-form-type-text UserSearchField lia-search-input-user search-input lia-js-hidden lia-autocomplete-input"
aria-label="Enter a user name or rank" value="" id="userSearchField_3ba3feee409c27" name="userSearchField" type="text" aria-autocomplete="both" autocomplete="off">
<div class="lia-autocomplete-container" style="display: none; position: absolute;">
<div class="lia-autocomplete-header">Enter a user name or rank</div>
<div class="lia-autocomplete-content">
<ul></ul>
</div>
<div class="lia-autocomplete-footer">
<a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="KurdEahNkS31JIcWAT6mDqUkW1II8YLaoSiOsUFowu4." rel="nofollow" id="disableAutoComplete_3ba3feef0d61d2" href="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/Exchange/article-id/31221&t:cp=action/contributions/searchactions">Turn off suggestions</a>
</div>
</div>
<input title="Enter a search word" class="lia-form-type-text NoteSearchField lia-search-input-note search-input lia-js-hidden lia-autocomplete-input" aria-label="Enter a search word" value="" id="noteSearchField_3ba3feee409c27_0"
name="noteSearchField" type="text" aria-autocomplete="both" autocomplete="off">
<div class="lia-autocomplete-container" style="display: none; position: absolute;">
<div class="lia-autocomplete-header">Enter a search word</div>
<div class="lia-autocomplete-content">
<ul></ul>
</div>
<div class="lia-autocomplete-footer">
<a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="uk6zjuITDhAZy7cGSov3s1HYqMMJXkOJ50cQazwwkh4." rel="nofollow" id="disableAutoComplete_3ba3feef37756d" href="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/Exchange/article-id/31221&t:cp=action/contributions/searchactions">Turn off suggestions</a>
</div>
</div>
<input title="Enter a search word" class="lia-form-type-text ProductSearchField lia-search-input-product search-input lia-js-hidden lia-autocomplete-input" aria-label="Enter a search word" value="" id="productSearchField_3ba3feee409c27"
name="productSearchField" type="text" aria-autocomplete="both" autocomplete="off">
<div class="lia-autocomplete-container" style="display: none; position: absolute;">
<div class="lia-autocomplete-header">Enter a search word</div>
<div class="lia-autocomplete-content">
<ul></ul>
</div>
<div class="lia-autocomplete-footer">
<a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="ah7L62fWfJ_B6EjwQXGb3dkUOuW6Mingwt7YzCtr_QU." rel="nofollow" id="disableAutoComplete_3ba3feef616d4b" href="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/Exchange/article-id/31221&t:cp=action/contributions/searchactions">Turn off suggestions</a>
</div>
</div>
<input class="lia-as-search-action-id" name="as-search-action-id" type="hidden">
</span>
</span>
<span class="lia-cancel-search" tabindex="0">cancel</span>
</form>Name: form — POST https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.searchformv32.form.form
<form enctype="multipart/form-data" class="lia-form lia-form-inline SearchForm" action="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.searchformv32.form.form" method="post" id="form" name="form">
<div class="t-invisible"><input value="blog-id/Exchange/article-id/31221" name="t:ac" type="hidden"><input value="search/contributions/page" name="t:cp" type="hidden"><input
value="FX6No5ScvCgzZxzAQPV1F1tYDZ-E9tupaq-dv8WPQhDh3HyWmbe47ZvtyTQaoznb--iQhppcmD2AssbQtT1zN3uBSLCKdtd83EmGdyTjz8VsVKtcOfOwu1BGRkeIft0lDfQ3tHDSruCgvXiuZrDNFgf1KZiRcJQFtD94nExoKnFmXG3X2AAYlEdEZ7G87VuZIE4q2Nk_kG5_6jv_httxQrUNNOMagkL_ZHUpt-D9PEnQIT3x86lBiDlUWcxUuk-9OpyBV0K8y-BBW0Z_WlAgZ5Qb8gfD_dvucKzD-kBBQOrtj4jks01C97frnhJEo0pV2rqLIPdi_Y08Ro70qQufOp9-DtN6QRW7d6aN72K1_vN6STqxxISAiZh3hjQgZdJoi_Le4Eg9wiIDLseHTGnj1bs2DrudgbZrZoY69zs5fZXKbLC3Xw9l8W-ldqVSWAcJbdgQ6nJopBSJt9ge_TyzJNC-nEBRGlFD4WlnYBTUJdEIeu3AwnTfLPhTzUJD1DYoicAnopkYYp3UIRf4F_4ZgVGrQs9s_8a9Rol2UfQFPCMg-cnLEcntWxotVpLujbTpjs4ylVxjv5R-96RD9HOBruGWta866Q8LlxNTjcJo-u1MzdczeFrVP7CTAW6BQl0DvP-sFOnr-mSB2BZugIJ3NCE4Nr2Eu-gLFsp_f3c-OHsGewlqeHufBnhFRl6_HQuWV0WjTNrFXTeLCM3t9R7vQS7yuBogZ50YJt6Kc-XCUIcQVzuy8KQYv7avMG345YZESL10iliJi0cH8E059OPZtkO1G6zjdpWxh0p3mUmU3HEJ-fQbKE5XaFsB0dIF7PCkkvCl7G7VEqva1FlLWLJBjKYT04hk_D3kBY9oRkshNE5SZ40xsxnKE7O41d3CdwHJe3ecD-LfxirRwVhvPDFr_Z1XNojadYHT14P-4GmxQqHD8HD5fEQHHLourD_uBlCidK8sA63xrKRZVg9c6a1rFEGxDNJ1pogp7qGrgsoURey9jylPq1Gw3YxS0WT4sK5D8gq0jOtqGiezQBMz8JAp6i2JCCvYIS_DCjmtydvwZa2sPOyRRL62OSCoTLHTPBo8IEGOuD4njIvvghi3ZhZ40Zq8D0NcsyaSxXKLKTUGWlyHJpinanUbT5_RugU8dRsx_wbzS8Dwwqkrp713_oW1SNyDuW1gCDbb9a_ALb2Y-5s."
name="lia-form-context" type="hidden"><input value="BlogArticlePage:blog-id/Exchange/article-id/31221:searchformv32.form:" name="liaFormContentKey" type="hidden"><input
value="yDZKQFNI0U/sd9X4pbUemqvQQZw=:H4sIAAAAAAAAALWSzUrDQBSFr4Wuigiib6DbiajdqAhFUISqweBaZibTNJpk4sxNEzc+ik8gvkQX7nwHH8CtKxfmzxJbwaTUVZhzw/nOmblP79COD+FAC6r40OAyQOWyCF0ZaMOkjtgrJgOp/NHONtER810sP9nfIkGtoCuVQ2hI+VAQpKHQqO67hEslPJcRRrUgPZaKlOOxKzx7wxIYhZtX487b+stnC5b60MnZ0junvkBY7d/QETU8GjiGlUYKnP0kRFguwEcFeAHBe02Dm0pyobWV+Wid0sbP9u7g4/G1BZCE8QWc1U3kpzapWoqZ+S+SvoMHgPQ+ypGVj/IoC2dlqHZ8CWZdV7xljUqszZa43voPYNHkFE7qGkdaqKrl1Pm7wEqmV59gcYjGkQOJP25h6jyJnOlzRv4DUURusIWhknbEsWo5K002vhzNufG1WHmDLwdzh8gDBQAA"
name="t:formdata" type="hidden"></div>
<div class="lia-inline-ajax-feedback">
<div class="AjaxFeedback" id="feedback"></div>
</div>
<input value="QjBHOKixQ_JWehsGaXUE2qKgubTLmwOpC6oi2Ak3X4s." name="lia-action-token" type="hidden">
<input value="form" id="form_UIDform" name="form_UID" type="hidden">
<input value="" id="form_instance_keyform" name="form_instance_key" type="hidden">
<span class="lia-search-input-wrapper">
<span class="lia-search-input-field">
<span class="lia-button-wrapper lia-button-wrapper-secondary lia-button-wrapper-searchForm-action"><input value="searchForm" name="submitContextX" type="hidden"><input class="lia-button lia-button-secondary lia-button-searchForm-action"
value="Search" id="submitContext" name="submitContext" type="submit"></span>
<input placeholder="Search the community" aria-label="Search" title="Search" class="lia-form-type-text lia-autocomplete-input search-input lia-search-input-message" value="" id="messageSearchField_0" name="messageSearchField" type="text"
aria-autocomplete="both" autocomplete="off">
<div class="lia-autocomplete-container" style="display: none; position: absolute;">
<div class="lia-autocomplete-header">Enter a search word</div>
<div class="lia-autocomplete-content">
<ul></ul>
</div>
<div class="lia-autocomplete-footer">
<a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="7BXez8_-3p9STLCAuS5xAmlmZ_8A6MQnBDdfka0AVFs." rel="nofollow" id="disableAutoComplete_3ba3feefe2e568" href="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/Exchange/article-id/31221&t:cp=action/contributions/searchactions">Turn off suggestions</a>
</div>
</div>
<input placeholder="Search the community" aria-label="Search" title="Search" class="lia-form-type-text lia-autocomplete-input search-input lia-search-input-tkb-article lia-js-hidden" value="" id="messageSearchField_1"
name="messageSearchField_0" type="text" aria-autocomplete="both" autocomplete="off">
<div class="lia-autocomplete-container" style="display: none; position: absolute;">
<div class="lia-autocomplete-header">Enter a search word</div>
<div class="lia-autocomplete-content">
<ul></ul>
</div>
<div class="lia-autocomplete-footer">
<a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="Ju_KahpOXub-LuU2kS96uj0rx_13SnMgLvVthrl8824." rel="nofollow" id="disableAutoComplete_3ba3fef00b6f41" href="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/Exchange/article-id/31221&t:cp=action/contributions/searchactions">Turn off suggestions</a>
</div>
</div>
<input placeholder="Search all content" ng-non-bindable="" title="Enter a user name or rank" class="lia-form-type-text UserSearchField lia-search-input-user search-input lia-js-hidden lia-autocomplete-input"
aria-label="Enter a user name or rank" value="" id="userSearchField" name="userSearchField" type="text" aria-autocomplete="both" autocomplete="off">
<div class="lia-autocomplete-container" style="display: none; position: absolute;">
<div class="lia-autocomplete-header">Enter a user name or rank</div>
<div class="lia-autocomplete-content">
<ul></ul>
</div>
<div class="lia-autocomplete-footer">
<a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="0U28FRVaz7jemGFYq5baANChzD9MG9GQR6tTasRqSwQ." rel="nofollow" id="disableAutoComplete_3ba3fef0377bf1" href="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/Exchange/article-id/31221&t:cp=action/contributions/searchactions">Turn off suggestions</a>
</div>
</div>
<input title="Enter a search word" class="lia-form-type-text NoteSearchField lia-search-input-note search-input lia-js-hidden lia-autocomplete-input" aria-label="Enter a search word" value="" id="noteSearchField_0" name="noteSearchField"
type="text" aria-autocomplete="both" autocomplete="off">
<div class="lia-autocomplete-container" style="display: none; position: absolute;">
<div class="lia-autocomplete-header">Enter a search word</div>
<div class="lia-autocomplete-content">
<ul></ul>
</div>
<div class="lia-autocomplete-footer">
<a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="KxTj7igr9AEXPVLHu3PPtAaD-wskeXc0nyAPNBk1n80." rel="nofollow" id="disableAutoComplete_3ba3fef0600ba6" href="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/Exchange/article-id/31221&t:cp=action/contributions/searchactions">Turn off suggestions</a>
</div>
</div>
<input title="Enter a search word" class="lia-form-type-text ProductSearchField lia-search-input-product search-input lia-js-hidden lia-autocomplete-input" aria-label="Enter a search word" value="" id="productSearchField"
name="productSearchField" type="text" aria-autocomplete="both" autocomplete="off">
<div class="lia-autocomplete-container" style="display: none; position: absolute;">
<div class="lia-autocomplete-header">Enter a search word</div>
<div class="lia-autocomplete-content">
<ul></ul>
</div>
<div class="lia-autocomplete-footer">
<a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="mferlfKnfTVDHgbM88s_t1nzZihWu8rfJByZPNdfzR0." rel="nofollow" id="disableAutoComplete_3ba3fef08b6da1" href="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/Exchange/article-id/31221&t:cp=action/contributions/searchactions">Turn off suggestions</a>
</div>
</div>
<input class="lia-as-search-action-id" name="as-search-action-id" type="hidden">
</span>
</span>
<span class="lia-cancel-search">cancel</span>
</form>Text Content
We use optional cookies to improve your experience on our websites, such as through social media connections, and to display personalized advertising based on your online activity. If you reject optional cookies, only cookies necessary to provide you the services will be used. You may change your selection by clicking “Manage Cookies” at the bottom of the page. Privacy Statement Third-Party Cookies Accept Reject Manage cookies Skip to main content Microsoft Tech Community Home Community Hubs Community Hubs * Community Hubs Home * Products * Special Topics * Video Hub Close PRODUCTS (69) SPECIAL TOPICS (41) VIDEO HUB (851) MOST ACTIVE HUBS Microsoft Teams Microsoft Excel Windows Security, Compliance and Identity Office 365 SharePoint Windows Server Azure Exchange Microsoft 365 Microsoft Edge Insider .NET Sharing best practices for building any app with .NET. Microsoft FastTrack Best practices and the latest news on Microsoft FastTrack Microsoft Viva The employee experience platform to help people thrive at work MOST ACTIVE HUBS ITOps Talk Core Infrastructure and Security Microsoft Learn Education Sector Microsoft 365 PnP AI and Machine Learning Microsoft Mechanics Healthcare and Life Sciences Small and Medium Business Public Sector Internet of Things (IoT) Azure Partner Community Expand your Azure partner-to-partner network Microsoft Tech Talks Bringing IT Pros together through In-Person & Virtual events MVP Award Program Find out more about the Microsoft MVP Award Program. VIDEO HUB Azure Exchange Microsoft 365 Microsoft 365 Business Microsoft 365 Enterprise Microsoft Edge Microsoft Outlook Microsoft Teams Security SharePoint Windows Browse All Community Hubs Blogs Blogs Events Events * Events Home * Microsoft Ignite * Microsoft Build * Community Events Microsoft Learn Microsoft Learn * Home * Community * Blog * Azure * Dynamics 365 * Microsoft 365 * Security, Compliance & Identity * Power Platform * Github * Teams * .NET Lounge Lounge * 820K Members * 7,469 Online * 2.2M Discussions Search Enter a search word Turn off suggestions Enter a search word Turn off suggestions Enter a user name or rank Turn off suggestions Enter a search word Turn off suggestions Enter a search word Turn off suggestions cancel Turn on suggestions Showing results for Show only | Search instead for Did you mean: Sign In Sign In Enter a search word Turn off suggestions Enter a search word Turn off suggestions Enter a user name or rank Turn off suggestions Enter a search word Turn off suggestions Enter a search word Turn off suggestions cancel Turn on suggestions Showing results for Show only | Search instead for Did you mean: * Home * Exchange * Exchange Team Blog * Basic Authentication and Exchange Online – September 2021 Update * Back to Blog * Newer Article * Older Article BASIC AUTHENTICATION AND EXCHANGE ONLINE – SEPTEMBER 2021 UPDATE * Subscribe to RSS Feed * * Mark as New * Mark as Read * * Bookmark * Subscribe * * Email to a Friend * * Printer Friendly Page * Report Inappropriate Content By The Exchange Team Published Sep 23 2021 02:55 PM 265K Views Skip to footer content The_Exchange_Team Microsoft Sep 23 2021 02:55 PM BASIC AUTHENTICATION AND EXCHANGE ONLINE – SEPTEMBER 2021 UPDATE Sep 23 2021 02:55 PM In February 2021, we announced some changes to our plan for turning off Basic Authentication in Exchange Online. In summary, we announced we were postponing disabling Basic Auth for protocols in active use by your tenant until further notice, but that we would continue to disable Basic Auth for all protocols not being used. The overall scope of the program was also extended to include Exchange Web Services (EWS), Exchange ActiveSync (EAS), POP, IMAP, Remote PowerShell, MAPI, RPC, SMTP AUTH and OAB. Today, we are announcing that, effective October 1, 2022, we will begin to permanently disable Basic Auth in all tenants, regardless of usage, with the exception of SMTP Auth. Basic Authentication is an outdated industry standard, and threats posed by Basic Auth have only increased in the time since we originally announced we were making this change. The original announcement was titled ‘Improving Security – Together’ and that’s never been truer than it is now. We need to work together to improve security. We take our role in that statement seriously, and our end goal is turning off Basic Auth for all our customers. But every day Basic Auth remains enabled in your tenant, your data is at risk, and so your role is to get your clients and apps off Basic Auth, move them to stronger and better options, and then secure your tenant, before we do. Even though we announced we were putting the work on hold, we didn’t stop improving security. Back in June we provided an update that we had already begun to disable Basic Auth for tenants not using it, and we described the process. We also explained how you could re-enable an affected protocol if you really needed to use it. This work has already protected millions of Exchange Online users. Today, we have more news on how to prepare for this important change. PROACTIVE PROTECTION EXPANSION In 2022, as we roll out the changes necessary to support this effort, we will begin disabling Basic Auth for some customers with usage on a short-term and temporary basis. IMPORTANT: Sometime in second quarter of 2022 we will selectively pick tenants and disable Basic Auth for all affected protocols except SMTP AUTH for a period of 12-48 hours. After this time, Basic Auth for these protocols will be re-enabled, if the tenant admin has not already re-enabled them using our self-service tools. During this time all clients and apps that use Basic Auth in the selected tenants will be affected, and they will be unable to connect. Any client or app using Modern Auth will not be affected. Users can switch to other clients (for example, use Outlook on the Web instead of an older Outlook client that does not support Modern Auth) while they upgrade or reconfigure their client apps. LIMITED OPT OUT If you receive a Message Center post between now and October 2022, informing you that we are going to disable Basic Auth for a protocol in your tenant due to non-usage, or you get one saying we know you are using Basic Auth, but we intend to proactively disable it for a short period of time, and you don’t want us to take that action for protocols in your tenant, you can use a new feature in the Microsoft 365 admin center to request that we not disable specific protocol(s). We added this feature to the self-service tool to help you minimize disruptions as you transition away from using Basic Auth. But we really want you to use this feature only if you really need Basic Auth. Not just because you think you might, or just in case. Customers are compromised through Basic Auth every day, and the best way to prevent that happening is to disable it and move to Modern Auth. The exception process was outlined in an earlier blog post but here it is again, with specifics for ‘opt out’ requests. You can now go directly to the Basic Auth self-help diagnostic by simply clicking on this button: (it’ll bring up the diagnostic in the Microsoft 365 admin center if you’re the tenant admin): Or you can open the Microsoft 365 admin center and click the green Help and support button in the lower right hand corner of the screen. When you click the button, you enter our self-help system. Here you can enter the magic phrase “Diag: Enable Basic Auth in EXO”: Whichever path you took to get here, click Run Tests to check your tenant settings to see if we have disabled Basic Auth for any protocols, and then review the results. If we have not disabled Basic Auth for any protocols in your tenant, and you are running the diagnostic before September 1, 2022 (one month before the October 2022 start date), we’ll offer you the option to opt out. Select the protocol to opt out from the dropdown, click the check box, and then click Update Settings. Repeat this process for each protocol to opt out. That’s it. Once you submit your opt out request, we won’t disable Basic Auth for the selected protocol(s) in your tenant, whether there is usage or not, until October 2022. Every tenant can request an opt out for each protocol (or set of protocols in the case of Outlook), until the start of September 2022. Starting September 1, 2022, we will remove the opt out option, and starting October 1, 2022, we’ll begin turning off Basic Auth in all tenants, regardless of usage. Note: Self service re-enablement of Basic Auth does not currently work for GCC tenants. For GCC tenants, please open a ticket with our support team to re-enable Basic Auth. To reiterate, requesting an opt out for protocols you aren’t sure about, or just in case, puts your tenant data at risk. If you really aren’t sure, let us turn it off and wait to see what happens (or use Security Defaults or Conditional Access to do it today). You can always re-enable it for the time being using the opt out process, and while this might cause some disruption, the upside is it will help you identify the affected clients and apps, and the work you need to do prior to October 2022. FREQUENTLY ASKED QUESTIONS How do I know if my tenant is using Basic Auth? Take a look at the Azure AD Sign-In log, as it can help identify ‘unexpected’ usage. We’re also going to start sending Message Center posts to tenant admins summarizing their usage (or lack of). How will I know if this change will affect my tenant? If the Azure AD Sign-In log shows Basic (legacy) Auth usage, this change will affect your tenant. I thought you said you were not going to completely disable SMTP AUTH? You’re right, we did, in blog posts here and here. We’re going to continue to disable SMTP AUTH for tenants who don’t use it, but we will not be changing the configuration of any tenant who does. We can’t tell though if the usage we see is valid or not, that’s down to you to determine. So you still should move away from using Basic and SMTP AUTH though if you can, as it does leave you exposed. Don’t forget, you can disable it at the tenant level, and re-enable on a per-user/account level as described here. I can’t re-enable SMTP using this feature, but I can request an opt out – huh? Well spotted! We didn’t build logic into the re-enablement tool for SMTP as you can already do that easily using PowerShell, but we wanted to make sure you could request an opt out for disabling of SMTP AUTH, so we included it here. How can I get a longer exception? I still want to use Basic Auth after October 2022 We are not providing the ability to use Basic Auth after October 2022. You should ensure your dependency on Basic Auth in Exchange Online has been removed by that time. Basic authentication (outside of SMTP) will be turned off for everyone in October 2022, including tenants who have previously opted out using our self-service tool. What if I request an opt out, do the necessary work, and then want you to disable Basic Auth? First of all, we’ll say well done, we appreciate you doing the work. Then, what we would advise would be to use Security Defaults or Conditional Access to block legacy auth. We might not get to your tenant right away, so better for you to take action and secure your tenant when you are ready, and then we’ll come back and disable it fully in time. What if you’ve blocked some protocols, but I want to request an exception for others? You won’t see the opt out dialog unless no protocols in your tenant are blocked. But that’s ok, as all you have to do is ‘re-enable’ that protocol (even though it’s not disabled at the time), and we’ll consider that an opt out request for it. If I’ve set up Authentication Policies, or Conditional Access to block legacy auth, how will I know it’s safe to remove these and not re-open myself to the risks posed by Basic Auth? Keep watching the Message Center in your tenant; we’ll send Message Center posts in advance of us making a change to your Basic Auth configuration, and again once we’ve made the change. What about Office 365 operated by 21Vianet? Is that subject to this change too? Yes it is, but the timeline is slightly different. We will turn off basic auth for all covered protocols on March 31st 2023. There will be no Proactive Protection Expansion as detailed above, but we will start to turn off basic auth for unused protocols during 2022. What are you doing with Application Access Policies? We’ve been trying to get our apps to use these to secure them more granularly, but with only 100 policies available, that’s impossible! We know many of our larger customers are already working on migrating thousands of service principals to our modern APIs, and we’ve heard the feedback that the existing limits with the current Application Access Policies code which allow only 300 service principals (we've increased from 100 to 300) is not enough. We’re announcing today that we plan on supporting 10,000 or more of these assignments per tenant. We’ll have more news on this update soon, so don’t let this issue stop you; it’s time to start planning to migrate your Basic Auth and legacy API applications to Microsoft Graph and Modern Authentication. While we’re on the subject of Application Access Policies, we also want to say that we are aligning our Application and Administrative access control models to allow the full flexibility of Role-Based Access Control to apply to service principals in Exchange Online. And we’re bringing a unified management experience for scoped application access to the Azure AD Identity portal where admin permission consents are managed today. More details will be announced soon! SUMMARY We know many of you will be happy about this announcement, as shutting down Basic Auth access to Exchange Online is a very good thing from a security perspective. And we also know that many of our customers have been focusing on other problems over the past year, and this will mean they might need to do more work in this area to be ready on time. We hope that giving you 12 months’ notice will give you sufficient time to prepare. The Exchange Online Team * Tags: * Basic Auth * Exchange Online 12 Likes Like 140 Comments kDylanHayes Senior Member Sep 23 2021 03:22 PM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 23 2021 03:22 PM Thank you guys for going back to the hardline stance. This is fantastic news and gets my full support, keep it up Microsoft! 4 Likes Like Mike Crowley Occasional Contributor Sep 23 2021 03:38 PM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 23 2021 03:38 PM Peel this band-aid off already! 3 Likes Like Jonas Back Frequent Contributor Sep 23 2021 11:16 PM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 23 2021 11:16 PM Awesome. Keep it up and don't back down! 2 Likes Like Groupsupport Occasional Visitor Sep 24 2021 01:37 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 01:37 AM How does this affect scanners and MFC devices using SMTP AUTH for scan to email? Will they all fail come when this change goes live? 13 Likes Like Cameron Gocke Contributor Sep 24 2021 05:03 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 05:03 AM My question is also about MFC / MFP devices using SMTP for scan to email and how those should be managed. 10 Likes Like CISUPOORT Frequent Visitor Sep 24 2021 05:14 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 05:14 AM . 2 Likes Like Fenner42 Occasional Visitor Sep 24 2021 05:33 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 05:33 AM Microsoft needs to keep this around to support legacy equipment like MFC, MFP and other such devices not designed for modern authentication. Telling us to upgrade or buy new is not very eco friendly. We are not going to get rid of a piece of well working equipment just because Microsoft wants to be communist by dictating to what they think everyone should have or use. 3 Likes Like kDylanHayes Senior Member Sep 24 2021 05:43 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 05:43 AM @CISUPOORT 2FA/MFA is unrelated to disabling basic auth, disabling basic auth and moving to modern auth does not require you to use Microsoft's MFA. You can always use solutions like Duo, Okta and many others for alternative MFA solutions. @The_Exchange_Team Can you guys clarify your stance on SMTP AUTH? will you guys be disabling it effective October 1, 2022 as well? "The overall scope of the program was also extended to include Exchange Web Services (EWS), Exchange ActiveSync (EAS), POP, IMAP, Remote PowerShell, MAPI, RPC, SMTP AUTH and OAB." 1 Like Like CISUPOORT Frequent Visitor Sep 24 2021 06:11 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 06:11 AM . 1 Like Like Mike Crowley Occasional Contributor Sep 24 2021 06:15 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 06:15 AM @CISUPOORTThere are a lot of hacking methods that exploit how simple it is to run many combinations through basic authentication. Even if you implement modern authentication (sometimes called web authentication) and no other security controls, you protect your users from a variety of password attacks. In addition, additional login metadata is sent as part of your authentication, and authentication / risk decisions can be based on this. As others have said, this paves the way for MFA, but that's a completely different topic. Also, shared mailboxes work fine with MFA. Unless you had multiple people sharing a PASSWORD, in which case, you should stop doing that. 2 Likes Like DBASQL775 Established Member Sep 24 2021 06:34 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 06:34 AM Cameron, Kdaylenhayes and groupsupport are correct we need to be crystal clear on this. Please tell us you understand by doing this procedure you will disabling scan to email for every printer on the planet. That has nothing to do with security, it's an absolute requirement even for a lot of military based devices. This seems insanely obvious but so does not asking admins to enter secret questions that we will have no idea of the answers in Windows 10 Pro setup so it must be specifically asked. 2 Likes Like Mike Crowley Occasional Contributor Sep 24 2021 06:37 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 06:37 AM Only if those copiers are sending to recipients outside of your tenant do they need* to use SMTP Auth. Most of the time, a user walks up, scans something to themselves and then uses Outlook, etc to send along elsewhere if necessary. If your MFC doesn't support modern auth, 2 of 3 scenarios in the article still apply: https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-dev... e. * not "need", but easier. 4 Likes Like DBASQL775 Established Member Sep 24 2021 06:49 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 06:49 AM Mike, No offense but thats not a good answer, there are so many legitimate use cases for these types of services. I have no doubt they will force this because they dont understand what daily use cases are but that doesn't make it smart or the correct choice. When you have suits making these decisions with no understanding of what they actual mean in the field its always going to be this way. What about website contact forms? Are you going to use the auth app to approve that account every time the token gets renewed? I am sure there are many many more things I am not thinking of at the moment that will be affected. In the end it probably wont matter, shills will shill and MS will just pull the trigger and after it shells everyone they will recant, re-enable, provide hack work arounds and on and on. 2 Likes Like Mike Crowley Occasional Contributor Sep 24 2021 06:53 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 06:53 AM None taken! I'm commenting so that at least some percentage of the readers can go away with alternate solutions. I get that some are going to have heartburn over this - but TBF, this is like 10 years in the making... A website contact form could just use a shared secret or cert with application permissions, no? 2 Likes Like Greg Taylor - EXCHANGE Microsoft Sep 24 2021 07:09 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 07:09 AM SMTP AUTH - As mentioned in Basic Authentication and Exchange Online – July Update - Microsoft Tech Community and Basic Authentication and Exchange Online – February 2021 Update - Microsoft Tech Community we will not be completely disabling SMTP AUTH for those customers that still want to use it. We will only be disabling it for tenants we don't see using it. We'll clarify that in the blog above shortly. Sorry for any confusion. 6 Likes Like HSI2020 Regular Visitor Sep 24 2021 07:13 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 07:13 AM @Mike Crowley 100% agree. When we migrate new customers to Office 365 that have MFD, legacy applications/services, etc.. we have them route/relay through a connector on their Hybrid Exchange Server or other on-premises SMTP Relay service/appliance to Office 365. It's a simple solution for those devices and apps that need to relay to users outside the org via Office 365, but can't or don't need to login into a mailbox or do SMTP Auth and I have yet to see a customer where this solution doesn't work. 3 Likes Like DBASQL775 Established Member Sep 24 2021 07:19 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 07:19 AM Hi Mike Yes I think something like that can be done as long as you dont mind being forced further in to Azure but even that currently has lots of confusion surrounding it. I am more bringing that up as another example, I am sure there are a lot more.... https://techcommunity.microsoft.com/t5/azure-active-directory-identity/update-your-applications-to-u... The point is its always done in an inconsistent way not matter what the roll out is. How can you have this many resources at your disposal and still have things this whacked out? Is it really necessary to have a major change notification 10 times a week. Can anyone really keep up with 30k users things are just endlessly changing for no good reason other than to move things around and charge more? Why not just charge more for E3 if you are so worried about security rather than saying hey if you want security you need P2 blah blah blah. It been abundantly clear for a long time those making the decisions have no idea what it means to this in the trenches. Its just endless non sense. 1 Like Like DBASQL775 Established Member Sep 24 2021 07:25 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 07:25 AM HSI There are many small firms that don't have those resources at their disposal. There are lots of use cases that are outside each of our point of view. That is also a work around that should not be needed. Anyway its Friday have a good day! 3 Likes Like Greg Taylor - EXCHANGE Microsoft Sep 24 2021 07:37 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 07:37 AM @CISUPOORT - you can move to Modern Auth without requiring/enforcing MFA. Your creds in the first instance are used to get tokens, from them on, it's just about refreshing tokens for continued access. 3 Likes Like JPogue Occasional Visitor Sep 24 2021 12:05 PM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 12:05 PM Basic auth is currently disabled in our tenant with an organizational level default Authentication Policy.: Set-OrganizationConfig -DefaultAuthenticationPolicy <PolicyIdentity> However, we have a small subset of accounts which still require basic auth for EWS and IMAP so we have a second Authentication Policy which allows basic auth over these protocols, and this policy is applied individually to these accounts. This works as described in this doc: Note that the authentication policies assigned to users take precedence over the default policy. To ... When Microsoft disables basic auth in Oct 2022, will that override and break the Authentication Policy-based exception we have applied to our small subset of accounts which still need basic auth over EWS and IMAP? 4 Likes Like Nino Bilic Microsoft Sep 24 2021 01:20 PM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 01:20 PM @JPogue Yes. After Oct 2022, Basic Auth will be disabled service-side. 3 Likes Like RyanWalker Regular Visitor Sep 24 2021 01:52 PM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 01:52 PM Not an Exchange admin by trade (so I apologize if I'm way off base), but we have several PowerShell scripts that require connecting to Exchange Online for tasks other than managing mailboxes (M365 Group management, audit searches, legal holds, etc...). Will the Exchange Online V2 PowerShell module be affected by this change? It currently requires Basic Authentication to be useful. When connecting from a client where Basic Auth is disabled I get this error: > WARNING: Please note that you can only use above 9 new EXO cmdlets (the one > with *-EXO* naming pattern).You can't use other cmdlets as we couldn't > establish a Remote PowerShell session as basic auth is disabled in your client > machine. To enable Basic Auth, please check instruction here > https://docs.microsoft.com/en-us/powershell/exchange/exchange-online-powershell-v2?view=exchange-ps#... > > > > New-ExoPSSession : Create Powershell Session is failed using OAuth > At C:\Program > Files\WindowsPowerShell\Modules\ExchangeOnlineManagement\2.0.4\netFramework\ExchangeOnlineManagement.psm1:475 > char:30 > + ... PSSession = New-ExoPSSession -ExchangeEnvironmentName $ExchangeEnviro > ... > + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > + CategoryInfo : NotSpecified: (:) [New-ExoPSSession], Exception > + FullyQualifiedErrorId : > System.Exception,Microsoft.Exchange.Management.ExoPowershellSnapin.NewExoPSSession 2 Likes Like Mike Crowley Occasional Contributor Sep 24 2021 01:56 PM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 01:56 PM @RyanWalkerare you referring to the client-side basic auth as discussed here? https://www.stigviewer.com/stig/windows_10/2020-06-15/finding/V-63335 If so, this is not what this article is about. The ExchangeOnlineManagement powershell module works with modern authentication / "legacy authentication" disabled on the tenant. 1 Like Like DoveFromAbove Occasional Contributor Sep 24 2021 01:59 PM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 01:59 PM Here we go again. We're a 4 fte company and I'm the Office 365 admin. The product is supposed to be ideal for small companies that do not have the resources to run their own server. No IT management knowledge required. Almost every day I get at least one "major change update notification" from the message center pointing me to pages like this one. I have NO IDEA what this is about but it scares the hell out of me. Every month something changes on our desktop keeping us from our own core business. Please, please, Microsoft, make something like Office 365 Small Business Basic LTS. We do appreciate to have our documents synchronized across all our devices but for the rest.... The Office 2003 apps would do the job for us. 2 Likes Like RyanWalker Regular Visitor Sep 24 2021 02:07 PM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 02:07 PM @Mike Crowley, yes that's the client-side setup I'm referring to. I just saw that Basic Auth was being disabled and remember seeing the warning message that I referenced above almost every day when I run my scripts from the wrong client. Wanted to make sure that Microsoft wasn't requiring mutually exclusive settings (the support documentation referenced in the warning message that I provided shows/requires the exact opposite of the article that you referenced). Thanks! 2 Likes Like HSI2020 Regular Visitor Sep 24 2021 02:33 PM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 02:33 PM @DoveFromAbove All these clients support modern authentication: * Outlook 2013 or later (Outlook 2013 requires a registry key change. See Enable Modern Authentication for Office 2013 on Windows devices for more information.) * Outlook 2016 for Mac or later * Outlook for iOS and Android * Mail for iOS 11.3.1 or later Google is also headed down this path, but they have frozen their timeline temporarily. Google Workspace Updates: Less secure app turn-off suspended until further notice (googleblog.com) It's just matter of time. 5 Likes Like kwester-ebbinghaus-business Contributor Sep 24 2021 04:02 PM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 24 2021 04:02 PM @The_Exchange_Team just in time, have you heard about this publication on Autodiscover and how easy it was to use autodiscover.com.anyTLD to phish for BASIC authentication? I am not a sec expert but I hope that this measure will at least be one part of the puzzle. 1 Like Like ajc196 Contributor Sep 25 2021 05:44 PM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 25 2021 05:44 PM Wish the past dates had stuck, but I appreciate the hard stance once again! Ironically once basic authentication is dead, we'll likely be re-enabling legacy protocols like IMAP/EAS on mailboxes to gives users more flexibility in 3rd party apps. If basic auth is not functional, they have to use something that supports that protocol *with* Modern Authentication. (e.g. Thunderbird currently supporting IMAP with OAuth 2.0) If it supports it, great, they do their MFA and carry on. If it doesn't, it just doesn't work because basic auth is dead. Right now we selectively enable IMAP on mailboxes but block basic auth for specific users via Conditional Access, so the above will let us stay hands-off again while allowing these 3rd party apps. 1 Like Like Greg Taylor - EXCHANGE Microsoft Sep 25 2021 05:58 PM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 25 2021 05:58 PM @ajc196 All the protocols that use Basic Auth and that we are shutting off already support OAuth already - so keep the protocol, just fix up the auth if you can. 1 Like Like ajc196 Contributor Sep 25 2021 06:04 PM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 25 2021 06:04 PM @Greg Taylor - EXCHANGE Yep, we are aware but we have a web of CA policies still allowing basic auth for various sets of conditions/scenarios that are still being addressed across several services, so we're not "untangling" said mess just yet. Basic auth being disabled & legacy protocols on by default is our ultimate goal. 1 Like Like Greg Taylor - EXCHANGE Microsoft Sep 25 2021 06:22 PM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 25 2021 06:22 PM @ajc196 ok, not sure I entirely follow, but it sounds like you know what you need to do. So good luck. Make sure you follow the opt out steps above so we don't touch your tenant inadvertently between now and October 2022. 1 Like Like ExchangeOnline Frequent Visitor Sep 26 2021 12:14 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 26 2021 12:14 AM @The_Exchange_Team We fully support turning off basic authentication! But please let the Outlook team add support for modern authentication in Outlook with POP/IMAP. Now this is not available, but this functionality is very much needed! 3 Likes Like Greg Taylor - EXCHANGE Microsoft Sep 26 2021 12:27 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 26 2021 12:27 AM @ExchangeOnline If you have Outlook, why use POP/IMAP? There are no plans to add support for Modern Auth to Outlook. If you have Outlook, use MAPI/HTTP. 1 Like Like ExchangeOnline Frequent Visitor Sep 26 2021 02:12 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 26 2021 02:12 AM @Greg Taylor - EXCHANGE For some mailboxes there is a security requirement to immediately dowload the messages using POP. Modern Auth in Exchange Online is available for POP, why not allowing it to use with Outlook? 2 Likes Like Greg Taylor - EXCHANGE Microsoft Sep 26 2021 09:12 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 26 2021 09:12 AM @ExchangeOnline Why does a 'security requirement' determine the protocol that has to be used? Why POP? Why not IMAP? or EWS? or MAPI? If this is an app, use EWS, or even better, REST/Graph. 1 Like Like ExchangeOnline Frequent Visitor Sep 26 2021 02:55 PM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 26 2021 02:55 PM @Greg Taylor - EXCHANGE we are familiar with the alternatives, but as you know POP, by default, removes the downloaded messages from the server. The consequence of forcing Modern Auth means that POP/IMAP on Exchange Online with Outlook cannot be used anymore, that would be very dissapointing. 1 Like Like Kevin_Hamilton Senior Member Sep 26 2021 07:20 PM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 26 2021 07:20 PM The FAQs state that "the Azure AD Sign-In log" can inform an administrator if there are existing uses of Basic Auth in the tenant. However, it does not indicate how you do that. How do I do that? Looking at the Azure AD Sign-in log, I don't see any obvious fields being reported that indicate if Basic Auth was used for the sign-in. 1 Like Like Jonas Back Frequent Contributor Sep 26 2021 11:34 PM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 26 2021 11:34 PM @Kevin_Hamilton Check the ”Client apps” kolumn in Sign-in logs and you can filter on Modern Authentication apps and not. 2 Likes Like QuiltersICT Occasional Visitor Sep 27 2021 05:54 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 27 2021 05:54 AM I run the office365 logins for a school. I'm not up with the lingo, so an idiots guide to this change would be good, to enable me to understand if I need to do anything to my school setup or if this will effect us in any way or not - will we notice any change? 1 Like Like Damon Villar Established Member Sep 27 2021 06:27 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 27 2021 06:27 AM If MAPI is going away how will the Outlook client connect? 1 Like Like JanisZ595 Occasional Visitor Sep 27 2021 06:34 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 27 2021 06:34 AM Hello. Will this change affect also SharePoint online? I see in Azure Sign-in logs: Application: Office 365 SharePoint Online Client app: Other clients If I understood correctly "other clients" is Legacy authentication client. 1 Like Like dhut500 Occasional Visitor Sep 27 2021 07:06 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 27 2021 07:06 AM @Fenner42 - You are able to use Direct Send, or any other number of options. Microsoft is not holding security efforts because you are unable to learn technology. Further -- If you actually read the article in its entirety, SMTP Auth is the exception. 2 Likes Like Mike Crowley Occasional Contributor Sep 27 2021 07:20 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 27 2021 07:20 AM >If MAPI is going away how will the Outlook client connect? @Damon Villar 1) IMAP is not MAPI 2) They aren't turning off MAPI or IMAP 3) They are turning off Basic / "Legacy" Authentication, but Exchange Online supports Modern Authentication for both IMAP and MAPI. 4) Most IMAP clients don't support Modern Auth. For example, Thunderbird does, but Outlook doesn't. However Outlook has no need to, since it it also supports (MAPI + Modern Authentication), which is a much more capable protocol. 1 Like Like Damon Villar Established Member Sep 27 2021 08:01 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 27 2021 08:01 AM In the article it states that MAPI is included in the list of protocols to be disabled. If this is the case than wouldn't full Outlook clients be effected by this? Should the Outlook client be using MapiHttp instead of just Mapi? The overall scope of the program was also extended to include Exchange Web Services (EWS), Exchange ActiveSync (EAS), POP, IMAP, Remote PowerShell, MAPI, RPC, SMTP AUTH and OAB. 1 Like Like Lyle_Epstein Frequent Visitor Sep 27 2021 08:05 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 27 2021 08:05 AM With basic auth being disabled in 2022, will we still be able to use SMTP relay as mentioned in this article https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-dev... . We use this method with IIS 6 (couldn't find the MS article anymore so this one is the same) https://support.datasharp.uk.com/portal/en-gb/kb/articles/how-to-configure-iis-for-relay-with-office... Will this now not work with IIS 6 method once Basic Auth is turned off? What are our alternatives when the deadline hits? 1 Like Like Mike Crowley Occasional Contributor Sep 27 2021 08:06 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 27 2021 08:06 AM @Damon Villar No, this article does not discuss disabling any protocols. This article discusses disabling legacy authentication. This concept has been the discussion of various Ehlo blog posts for the better part of a decade. Checkout some of these other articles: https://duckduckgo.com/?q=%22modern+authentication%22+site%3Atechcommunity.microsoft.com%2Ft5%2Fexch... 1 Like Like MichaelN645 Frequent Visitor Sep 27 2021 08:42 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 27 2021 08:42 AM What about unattended Powershell scripts (or other system services) that need authentication? 2 Likes Like ajc196 Contributor Sep 27 2021 08:45 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 27 2021 08:45 AM @MichaelN645 Certificate-based authentication: https://docs.microsoft.com/en-us/powershell/exchange/app-only-auth-powershell-v2?view=exchange-ps 4 Likes Like Mike Crowley Occasional Contributor Sep 27 2021 08:53 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 27 2021 08:53 AM @MichaelN645 If you previously used Send-MailMessage, you can move to Send-MgUserMessage. Shameless plug here: https://mikecrowley.us/2021/09/25/send-mgusermessage/ If you want to see how modern auth works with Thunderbird, check out Michel de Rooij's post here: https://eightwone.com/2020/07/01/configuring-exchange-account-with-imap-oauth2/ If you have more complex needs, check out Glen Scales' numerous, high-quality articles: https://gsexdev.blogspot.com/search?q=%22modern+auth%22 3 Likes Like Greg Taylor - EXCHANGE Microsoft Sep 27 2021 09:03 AM * Mark as Read * Mark as New * * Bookmark * * Permalink * Print * Email to a Friend * * Report Inappropriate Content Sep 27 2021 09:03 AM @QuiltersICT - as the first FAQ says, start here, or you wait for our MC posts to arrive. Start with the report would be my advice. How do I know if my tenant is using Basic Auth? Take a look at the Azure AD Sign-In log, as it can help identify ‘unexpected’ usage. We’re also going to start sending Message Center posts to tenant admins summarizing their usage (or lack of). @Lyle_Epstein SMTP is not being turned off if it's being used in your tenant. Please read the blog and FAQ's again. @Damon Villar As @Mike Crowley said, we're not disabling any protocols, only specific auth types. They are not the same thing. MAPI(http, you are right, it's MAPI over HTTP, but we're just calling it MAPI in this case, but they are one and the same) is not being disabled. Basic Auth with MAPI is, but not OAuth. But yes, this change affects Outlook - but only if it is using Basic Auth with MAPI. 2 Likes Like * « Previous * * 1 * 2 * 3 * Next » You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in. * Comment Co-Authors The_Exchange_Team Version history Last update: Apr 05 2022 07:32 AM Updated by: The_Exchange_Team Labels * Announcements 371 * Exchange Online 250 * Security 127 SHARE * Share to LinkedIn * Share to Facebook * Share to Twitter * Share to Email Browse Skip to primary navigation WHAT'S NEW * Surface Pro X * Surface Laptop 3 * Surface Pro 7 * Windows 10 Apps * Office apps MICROSOFT STORE * Account profile * Download Center * Microsoft Store support * Returns * Order tracking * Store locations * Buy online, pick up in store * In-store events EDUCATION * Microsoft in education * Office for students * Office for schools * Deals for students and parents * Microsoft Azure in education ENTERPRISE * Azure * AppSource * Automotive * Government * Healthcare * Manufacturing * Financial Services * Retail DEVELOPER * Microsoft Visual Studio * Window Dev Center * Developer Network * TechNet * Microsoft developer program * Channel 9 * Office Dev Center * Microsoft Garage COMPANY * Careers * About Microsoft * Company News * Privacy at Microsoft * Investors * Diversity and inclusion * Accessibility * Security * Sitemap * Contact Microsoft * Privacy * Manage cookies * Terms of use * Trademarks * Safety and eco * About our ads * © 2022 Microsoft Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.