<?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>topic EWS O365 Instance - Not allowed to access Non IPM folder. (85) in Cortex XSOAR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/ews-o365-instance-not-allowed-to-access-non-ipm-folder-85/m-p/583082#M3225</link>
    <description>&lt;P&gt;XSOAR stopped fetching incidents from our assigned email address on April 3rd. I opened the EWS O365 instance to investigate and did a "test" for troubleshooting and the test result shows:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;DIV class="test-result-title"&gt;
&lt;DIV class="semi-bold"&gt;&lt;STRONG&gt;Error&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV class="test-timestamp"&gt;&lt;STRONG&gt;(April 9, 2024 11:14 AM)&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;P&gt;&lt;STRONG&gt;Not allowed to access Non IPM folder. (85)&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We did not make any settings changes to the instance. After doing some research it appears that there was a recent change with Microsoft O365. Is anyone else running into this issue? Is there a work around or fix?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;#EWSO365 #EWSO365Instance&lt;/P&gt;</description>
    <pubDate>Tue, 09 Apr 2024 17:29:49 GMT</pubDate>
    <dc:creator>WillNguyen</dc:creator>
    <dc:date>2024-04-09T17:29:49Z</dc:date>
    <item>
      <title>EWS O365 Instance - Not allowed to access Non IPM folder. (85)</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/ews-o365-instance-not-allowed-to-access-non-ipm-folder-85/m-p/583082#M3225</link>
      <description>&lt;P&gt;XSOAR stopped fetching incidents from our assigned email address on April 3rd. I opened the EWS O365 instance to investigate and did a "test" for troubleshooting and the test result shows:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;DIV class="test-result-title"&gt;
&lt;DIV class="semi-bold"&gt;&lt;STRONG&gt;Error&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV class="test-timestamp"&gt;&lt;STRONG&gt;(April 9, 2024 11:14 AM)&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;P&gt;&lt;STRONG&gt;Not allowed to access Non IPM folder. (85)&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We did not make any settings changes to the instance. After doing some research it appears that there was a recent change with Microsoft O365. Is anyone else running into this issue? Is there a work around or fix?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;#EWSO365 #EWSO365Instance&lt;/P&gt;</description>
      <pubDate>Tue, 09 Apr 2024 17:29:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/ews-o365-instance-not-allowed-to-access-non-ipm-folder-85/m-p/583082#M3225</guid>
      <dc:creator>WillNguyen</dc:creator>
      <dc:date>2024-04-09T17:29:49Z</dc:date>
    </item>
    <item>
      <title>Re: EWS O365 Instance - Not allowed to access Non IPM folder. (85)</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/ews-o365-instance-not-allowed-to-access-non-ipm-folder-85/m-p/583092#M3226</link>
      <description>&lt;P&gt;Apparently the fix in the code is very simple, but if we don't want to clone and maintain our own integrations, we'll have to wait for the update.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The fix is described here.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://stackoverflow.com/questions/78264205/not-allowed-to-access-non-ipm-folder" target="_blank"&gt;https://stackoverflow.com/questions/78264205/not-allowed-to-access-non-ipm-folder&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If we could get some XSOAR engineer to push this badboy, that'd pretty cool.&lt;/P&gt;</description>
      <pubDate>Tue, 09 Apr 2024 19:12:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/ews-o365-instance-not-allowed-to-access-non-ipm-folder-85/m-p/583092#M3226</guid>
      <dc:creator>CJNTS</dc:creator>
      <dc:date>2024-04-09T19:12:56Z</dc:date>
    </item>
    <item>
      <title>Re: EWS O365 Instance - Not allowed to access Non IPM folder. (85)</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/ews-o365-instance-not-allowed-to-access-non-ipm-folder-85/m-p/583096#M3228</link>
      <description>&lt;P&gt;Looks like there is a content pack update that addresses this in the marketplace.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV id="dropdown-expander-title" class="dropdown-expander-title clickable"&gt;
&lt;DIV class="expander-left-components"&gt;
&lt;DIV class="expander-label-wrapper title-h3"&gt;
&lt;DIV class="ui grid"&gt;
&lt;DIV class="ui row"&gt;
&lt;DIV class="ui column"&gt;
&lt;DIV class="pack-release-notes-version-header h4"&gt;1.3.3 - 940291 (April 7, 2024)&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="ui five wide right floated right aligned column"&gt;
&lt;DIV class="version-rn isInstalled"&gt;&lt;SPAN class="pack-install-link-wrapper"&gt;&lt;SPAN class="pack-install-link link-text"&gt;Reinstall 1.3.3&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN class="color-success installed-pack-release-notes"&gt;&lt;I class="demisto-icon icon-status-check-24-r"&gt;&lt;/I&gt;Installed&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="dropdown-expander-content pack-release-notes-version pack-release-notes-version-1.3.3 dropdown-expander-content-extended"&gt;
&lt;DIV class="global-markdown"&gt;
&lt;H4&gt;Integrations&lt;/H4&gt;
&lt;H5&gt;EWS O365&lt;/H5&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;U&gt;Fixed the &lt;STRONG&gt;ews-get-folder&lt;/STRONG&gt; command which failed when given a folder ID as &lt;EM&gt;&lt;STRONG&gt;folder-path&lt;/STRONG&gt;&lt;/EM&gt;.&lt;/U&gt;&lt;/LI&gt;
&lt;LI&gt;Fixed an issue in &lt;STRONG&gt;Fetch incident&lt;/STRONG&gt; with inline image attachments in &lt;EM&gt;PreprocessEmail&lt;/EM&gt; script by adding description field to attachments to distinguish file attachments from inline images.&lt;/LI&gt;
&lt;LI&gt;Updated the Docker image to: &lt;EM&gt;demisto/py3ews:1.0.0.91453&lt;/EM&gt;.&lt;/LI&gt;
&lt;/UL&gt;
&lt;H5&gt;EWS Extension Online Powershell v3&lt;/H5&gt;
&lt;DIV class="preplacer"&gt;Fixed an issue where the following commands returned an error when no response was received:&lt;/DIV&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;EM&gt;&lt;STRONG&gt;ews-new-tenant-allow-block-list-items&lt;/STRONG&gt;&lt;/EM&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;EM&gt;&lt;STRONG&gt;ews-get-tenant-allow-block-list-items&lt;/STRONG&gt;&lt;/EM&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;EM&gt;&lt;STRONG&gt;ews-get-tenant-allow-block-list-count&lt;/STRONG&gt;&lt;/EM&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;EM&gt;&lt;STRONG&gt;ews-remove-tenant-allow-block-list-items&lt;/STRONG&gt;&lt;/EM&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Tue, 09 Apr 2024 19:35:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/ews-o365-instance-not-allowed-to-access-non-ipm-folder-85/m-p/583096#M3228</guid>
      <dc:creator>CJNTS</dc:creator>
      <dc:date>2024-04-09T19:35:56Z</dc:date>
    </item>
    <item>
      <title>Re: EWS O365 Instance - Not allowed to access Non IPM folder. (85)</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/ews-o365-instance-not-allowed-to-access-non-ipm-folder-85/m-p/583104#M3229</link>
      <description>&lt;P&gt;Thanks!&lt;/P&gt;
&lt;P&gt;I updated the content pack - &lt;EM&gt;Microsoft Exchange Online&lt;/EM&gt; to latest version 1.3.3 and it is now working.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Appears a fix on April 5th addressed this "Not Allowed Access" error.&lt;BR /&gt;&lt;SPAN&gt;1.3.0 - R936713 (April 5, 2024)&lt;/SPAN&gt;&lt;/P&gt;
&lt;DIV id="dropdown-expander-title" class="dropdown-expander-title clickable"&gt;
&lt;DIV class="expander-left-components"&gt;
&lt;DIV class="expander-label-wrapper title-h3"&gt;
&lt;DIV class="ui grid"&gt;
&lt;DIV class="ui row"&gt;
&lt;DIV class="ui five wide right floated right aligned column"&gt;
&lt;DIV class="version-rn isDowngrade"&gt;&lt;SPAN&gt;Integrations&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="dropdown-expander-content pack-release-notes-version pack-release-notes-version-1.3.0 dropdown-expander-content-extended"&gt;
&lt;DIV class="global-markdown"&gt;
&lt;H5&gt;EWS O365&lt;/H5&gt;
&lt;UL&gt;
&lt;LI&gt;Fixed an issue where the integration has failed with ‘Not Allowed Access’ error due to breaking changes on Microsoft’s side.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Tue, 09 Apr 2024 20:37:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/ews-o365-instance-not-allowed-to-access-non-ipm-folder-85/m-p/583104#M3229</guid>
      <dc:creator>WillNguyen</dc:creator>
      <dc:date>2024-04-09T20:37:13Z</dc:date>
    </item>
  </channel>
</rss>

