<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Api-Deprecation on CuraSec</title><link>https://curasec.metacog.co.kr/tags/api-deprecation/</link><description>Recent content in Api-Deprecation on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 22 Oct 2026 15:52:23 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/api-deprecation/index.xml" rel="self" type="application/rss+xml"/><item><title>Microsoft offers EWS API re-enablement fix for Exchange Online</title><link>https://curasec.metacog.co.kr/insights/2026-10-22-microsoft-shares-how-to-fix-broken-exchange-online-ews-apps/</link><pubDate>Thu, 22 Oct 2026 15:52:23 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-22-microsoft-shares-how-to-fix-broken-exchange-online-ews-apps/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> If your org runs EWS-dependent apps against Exchange Online, audit those integrations and plan migration to Microsoft Graph API before EWS is permanently removed; re-enabling EWS is a temporary reprieve, not a long-term fix.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>