<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Important Idira Identity Notification regarding Microsoft Office 365 and Azure Portal in Workforce Identity Articles</title>
    <link>https://live.paloaltonetworks.com/t5/workforce-identity-articles/important-idira-identity-notification-regarding-microsoft-office/ta-p/1428516</link>
    <description>&lt;P&gt;Idira Identity supports single sign-on, automated provisioning, and adaptive multi-factor authentication capabilities for Microsoft Office 365 and Microsoft Azure Portal. Currently, Idira Identity supports two methods to authenticate and perform these functions in Office 365 and Azure Portal:&amp;nbsp;&lt;/P&gt;
&lt;OL start="1"&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Basic Authentication&lt;/STRONG&gt;: leverages Azure AD Connect V1 APIs to authenticate to Office 365 and Azure Portal using the user’s Microsoft account credentials.&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;OL start="2"&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Token-based Authentication&lt;/STRONG&gt;: leverages Microsoft Graph APIs to securely authenticate to Office 365 and Azure Portal using a modern token-based authentication protocol.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;P&gt;Microsoft has announced that as of 1st October 2023, they will stop supporting Azure AD Connect V1, and has advised customers to migrate to Azure AD Connect V2. You can see the notification &lt;A href="https://learn.microsoft.com/en-us/azure/active-directory/hybrid/decommission-connect-sync-v1" target="_blank"&gt;here&lt;/A&gt;.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Consequently, &lt;STRONG&gt;as of 1st October 2023, Idira Identity will no longer be able to support user provisioning to Microsoft Office 365 and Azure Portal using Basic Authentication.&lt;/STRONG&gt;&lt;/P&gt;
&lt;BR /&gt;If you currently use Basic Authentication (option 1 in the images below) for user provisioning to Office 365 and Azure Portal, you will be required to migrate to Token-Based Authentication (option 2 in the images below).&amp;nbsp;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZiPIAW__eid=ka3Ht000000LZiP&amp;amp;feoid=00N2J000009R3kl&amp;amp;refid=0EMHt000005vw53.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/98330iD6D8E2EBCC23DA90/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZiPIAW__eid=ka3Ht000000LZiP&amp;amp;feoid=00N2J000009R3kl&amp;amp;refid=0EMHt000005vw53.png" alt="ka3Ht000000LZiPIAW__eid=ka3Ht000000LZiP&amp;amp;feoid=00N2J000009R3kl&amp;amp;refid=0EMHt000005vw53.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZiPIAW__eid=ka3Ht000000LZiP&amp;amp;feoid=00N2J000009R3kl&amp;amp;refid=0EMHt000005vw5N.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/98331iF7704A872F95006A/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZiPIAW__eid=ka3Ht000000LZiP&amp;amp;feoid=00N2J000009R3kl&amp;amp;refid=0EMHt000005vw5N.png" alt="ka3Ht000000LZiPIAW__eid=ka3Ht000000LZiP&amp;amp;feoid=00N2J000009R3kl&amp;amp;refid=0EMHt000005vw5N.png" /&gt;&lt;/span&gt;
&lt;DIV id="" style="left: 20px;top: 749.75px;"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;H3&gt;Steps&lt;/H3&gt;
&lt;P&gt;To use Token-Based Authentication, you will need to sign in to your Azure Active Directory environment and obtain the token credentials. You can find the instructions &lt;A href="https://docs.cyberark.com/Idaptive/Latest/en/Content/Applications/AppsWeb/Office365/O365_ConfigInAdmin.htm?TocPath=Administrator%7CIntegrate%20apps%7CDeploy%20applications%20for%20SSO%7CCertified%20applications%7COffice%20365%20for%20CyberArk%20Identity%7C_____7" target="_blank"&gt;here&lt;/A&gt;.&amp;nbsp;&lt;/P&gt;
&lt;OL start="1"&gt;&lt;LI&gt;If you have been using &lt;STRONG&gt;Basic Authentication to provision users from the Idira Identity Cloud Directory&lt;/STRONG&gt;, please perform the following steps to migrate to Token-Based Authentication.&amp;nbsp;&amp;nbsp;

	&lt;OL&gt;&lt;LI&gt;
&lt;P&gt;Disable provisioning in the Office 365 or Azure Portal app using Basic Authentication.&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;OL start="2" style="margin-left: 40px;"&gt;&lt;LI&gt;
&lt;P&gt;Deploy a new Office 365 or Azure Portal app template, configured for Token-Based Authentication. For details see&amp;nbsp; &lt;A href="https://docs.cyberark.com/Idaptive/Latest/en/Content/Applications/AppsWeb/Office365/O365_ConfigInAdmin.htm" target="_blank"&gt;Configure Office 365 for single sign-on&lt;/A&gt; and &lt;A href="https://docs.cyberark.com/Idaptive/Latest/en/Content/Applications/AppsWeb/Azure_Portal_SSO.htm?tocpath=Administrator%7CIntegrate%20apps%7CDeploy%20applications%20for%20SSO%7CCertified%20applications%7C_____158" target="_blank"&gt;Configure Azure Portal&lt;/A&gt;. You can use the existing application that uses Basic Authentication as a reference for your single sign-on settings and provisioning role mappings.&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;OL start="3" style="margin-left: 40px;"&gt;&lt;LI&gt;
&lt;P&gt;Go to Settings &amp;gt; Users &amp;gt; Outbound Provisioning, then select your Office 365 or Azure Portal app using Token-Based Authentication from the Provisioning Enabled Applications drop-down menu and click Start Sync.&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;OL start="2"&gt;&lt;LI&gt;
&lt;P&gt;If you have been using &lt;STRONG&gt;Basic Authentication to provision users from Active Directory to Office 365 or Azure Portal&lt;/STRONG&gt;, see the steps &lt;A href="https://docs.cyberark.com/Idaptive/Latest/en/Content/Applications/AppsWeb/Office365/O365-migrate-to-TBA.htm?TocPath=Administrator%7CIntegrate%20apps%7CDeploy%20applications%20for%20SSO%7CCertified%20applications%7COffice%20365%20for%20CyberArk%20Identity%7C_____3" target="_blank"&gt;here&lt;/A&gt; to m&lt;A href="https://docs.cyberark.com/Idaptive/Latest/en/Content/Applications/AppsWeb/Office365/O365-migrate-to-TBA.htm" target="_blank"&gt;igrate Office 365 to Token-Based Authentication&lt;/A&gt;. The same steps need to be followed for Azure Portal app.&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;OL start="1" style="margin-left: 40px;"&gt;&lt;LI&gt;
&lt;P&gt;Token-Based Authentication uses Microsoft Graph APIs which do not support some attributes supported by Microsoft Web Services used with Basic Authentication.&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;OL start="2" style="margin-left: 40px;"&gt;&lt;LI&gt;
&lt;P&gt;Review the list of attributes to ensure that your functionality is not affected. See&amp;nbsp; &lt;A href="https://docs.cyberark.com/Idaptive/Latest/en/Content/Applications/AppsWeb/Office365/O365_TBA-vs-Basic-auth.htm?TocPath=Administrator%7CIntegrate%20apps%7CDeploy%20applications%20for%20SSO%7CCertified%20applications%7COffice%20365%20for%20CyberArk%20Identity%7C_____4" target="_blank"&gt;Differences in Attribute Support for Basic vs. Token-Based Authentication&lt;/A&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;OL start="3" style="margin-left: 40px;"&gt;&lt;LI&gt;
&lt;P&gt;If you require the above-mentioned attributes, then you may have to use Microsoft Azure AD Connect V2 to sync them from Active Directory to Azure AD.&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;OL start="3"&gt;&lt;LI&gt;
&lt;P&gt;The migration from basic authentication to Token Based Authentication does not have any impact on the Idira single sign-on or Adaptive MFA capabilities.&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;BR /&gt;Please contact your Idira Technical Account Manager or Idira Support Team for additional questions or support.&amp;nbsp;&amp;nbsp;&amp;nbsp;</description>
    <pubDate>Thu, 05 Nov 2026 20:01:03 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-11-05T20:01:03Z</dc:date>
    <item>
      <title>Important Idira Identity Notification regarding Microsoft Office 365 and Azure Portal</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-articles/important-idira-identity-notification-regarding-microsoft-office/ta-p/1428516</link>
      <description>&lt;P&gt;Idira Identity supports single sign-on, automated provisioning, and adaptive multi-factor authentication capabilities for Microsoft Office 365 and Microsoft Azure Portal. Currently, Idira Identity supports two methods to authenticate and perform these functions in Office 365 and Azure Portal:&amp;nbsp;&lt;/P&gt;
&lt;OL start="1"&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Basic Authentication&lt;/STRONG&gt;: leverages Azure AD Connect V1 APIs to authenticate to Office 365 and Azure Portal using the user’s Microsoft account credentials.&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;OL start="2"&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Token-based Authentication&lt;/STRONG&gt;: leverages Microsoft Graph APIs to securely authenticate to Office 365 and Azure Portal using a modern token-based authentication protocol.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;P&gt;Microsoft has announced that as of 1st October 2023, they will stop supporting Azure AD Connect V1, and has advised customers to migrate to Azure AD Connect V2. You can see the notification &lt;A href="https://learn.microsoft.com/en-us/azure/active-directory/hybrid/decommission-connect-sync-v1" target="_blank"&gt;here&lt;/A&gt;.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Consequently, &lt;STRONG&gt;as of 1st October 2023, Idira Identity will no longer be able to support user provisioning to Microsoft Office 365 and Azure Portal using Basic Authentication.&lt;/STRONG&gt;&lt;/P&gt;
&lt;BR /&gt;If you currently use Basic Authentication (option 1 in the images below) for user provisioning to Office 365 and Azure Portal, you will be required to migrate to Token-Based Authentication (option 2 in the images below).&amp;nbsp;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZiPIAW__eid=ka3Ht000000LZiP&amp;amp;feoid=00N2J000009R3kl&amp;amp;refid=0EMHt000005vw53.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/98330iD6D8E2EBCC23DA90/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZiPIAW__eid=ka3Ht000000LZiP&amp;amp;feoid=00N2J000009R3kl&amp;amp;refid=0EMHt000005vw53.png" alt="ka3Ht000000LZiPIAW__eid=ka3Ht000000LZiP&amp;amp;feoid=00N2J000009R3kl&amp;amp;refid=0EMHt000005vw53.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZiPIAW__eid=ka3Ht000000LZiP&amp;amp;feoid=00N2J000009R3kl&amp;amp;refid=0EMHt000005vw5N.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/98331iF7704A872F95006A/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZiPIAW__eid=ka3Ht000000LZiP&amp;amp;feoid=00N2J000009R3kl&amp;amp;refid=0EMHt000005vw5N.png" alt="ka3Ht000000LZiPIAW__eid=ka3Ht000000LZiP&amp;amp;feoid=00N2J000009R3kl&amp;amp;refid=0EMHt000005vw5N.png" /&gt;&lt;/span&gt;
&lt;DIV id="" style="left: 20px;top: 749.75px;"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;H3&gt;Steps&lt;/H3&gt;
&lt;P&gt;To use Token-Based Authentication, you will need to sign in to your Azure Active Directory environment and obtain the token credentials. You can find the instructions &lt;A href="https://docs.cyberark.com/Idaptive/Latest/en/Content/Applications/AppsWeb/Office365/O365_ConfigInAdmin.htm?TocPath=Administrator%7CIntegrate%20apps%7CDeploy%20applications%20for%20SSO%7CCertified%20applications%7COffice%20365%20for%20CyberArk%20Identity%7C_____7" target="_blank"&gt;here&lt;/A&gt;.&amp;nbsp;&lt;/P&gt;
&lt;OL start="1"&gt;&lt;LI&gt;If you have been using &lt;STRONG&gt;Basic Authentication to provision users from the Idira Identity Cloud Directory&lt;/STRONG&gt;, please perform the following steps to migrate to Token-Based Authentication.&amp;nbsp;&amp;nbsp;

	&lt;OL&gt;&lt;LI&gt;
&lt;P&gt;Disable provisioning in the Office 365 or Azure Portal app using Basic Authentication.&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;OL start="2" style="margin-left: 40px;"&gt;&lt;LI&gt;
&lt;P&gt;Deploy a new Office 365 or Azure Portal app template, configured for Token-Based Authentication. For details see&amp;nbsp; &lt;A href="https://docs.cyberark.com/Idaptive/Latest/en/Content/Applications/AppsWeb/Office365/O365_ConfigInAdmin.htm" target="_blank"&gt;Configure Office 365 for single sign-on&lt;/A&gt; and &lt;A href="https://docs.cyberark.com/Idaptive/Latest/en/Content/Applications/AppsWeb/Azure_Portal_SSO.htm?tocpath=Administrator%7CIntegrate%20apps%7CDeploy%20applications%20for%20SSO%7CCertified%20applications%7C_____158" target="_blank"&gt;Configure Azure Portal&lt;/A&gt;. You can use the existing application that uses Basic Authentication as a reference for your single sign-on settings and provisioning role mappings.&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;OL start="3" style="margin-left: 40px;"&gt;&lt;LI&gt;
&lt;P&gt;Go to Settings &amp;gt; Users &amp;gt; Outbound Provisioning, then select your Office 365 or Azure Portal app using Token-Based Authentication from the Provisioning Enabled Applications drop-down menu and click Start Sync.&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;OL start="2"&gt;&lt;LI&gt;
&lt;P&gt;If you have been using &lt;STRONG&gt;Basic Authentication to provision users from Active Directory to Office 365 or Azure Portal&lt;/STRONG&gt;, see the steps &lt;A href="https://docs.cyberark.com/Idaptive/Latest/en/Content/Applications/AppsWeb/Office365/O365-migrate-to-TBA.htm?TocPath=Administrator%7CIntegrate%20apps%7CDeploy%20applications%20for%20SSO%7CCertified%20applications%7COffice%20365%20for%20CyberArk%20Identity%7C_____3" target="_blank"&gt;here&lt;/A&gt; to m&lt;A href="https://docs.cyberark.com/Idaptive/Latest/en/Content/Applications/AppsWeb/Office365/O365-migrate-to-TBA.htm" target="_blank"&gt;igrate Office 365 to Token-Based Authentication&lt;/A&gt;. The same steps need to be followed for Azure Portal app.&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;OL start="1" style="margin-left: 40px;"&gt;&lt;LI&gt;
&lt;P&gt;Token-Based Authentication uses Microsoft Graph APIs which do not support some attributes supported by Microsoft Web Services used with Basic Authentication.&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;OL start="2" style="margin-left: 40px;"&gt;&lt;LI&gt;
&lt;P&gt;Review the list of attributes to ensure that your functionality is not affected. See&amp;nbsp; &lt;A href="https://docs.cyberark.com/Idaptive/Latest/en/Content/Applications/AppsWeb/Office365/O365_TBA-vs-Basic-auth.htm?TocPath=Administrator%7CIntegrate%20apps%7CDeploy%20applications%20for%20SSO%7CCertified%20applications%7COffice%20365%20for%20CyberArk%20Identity%7C_____4" target="_blank"&gt;Differences in Attribute Support for Basic vs. Token-Based Authentication&lt;/A&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;OL start="3" style="margin-left: 40px;"&gt;&lt;LI&gt;
&lt;P&gt;If you require the above-mentioned attributes, then you may have to use Microsoft Azure AD Connect V2 to sync them from Active Directory to Azure AD.&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;OL start="3"&gt;&lt;LI&gt;
&lt;P&gt;The migration from basic authentication to Token Based Authentication does not have any impact on the Idira single sign-on or Adaptive MFA capabilities.&amp;nbsp;&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;BR /&gt;Please contact your Idira Technical Account Manager or Idira Support Team for additional questions or support.&amp;nbsp;&amp;nbsp;&amp;nbsp;</description>
      <pubDate>Thu, 05 Nov 2026 20:01:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-articles/important-idira-identity-notification-regarding-microsoft-office/ta-p/1428516</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-11-05T20:01:03Z</dc:date>
    </item>
  </channel>
</rss>

