<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Authorization &amp; Permission Request on Virtosoftware Guides &amp; Docs</title><link>https://docs-hugo-4dl.pages.dev/docs/calendar-overlay-pro/installation-and-configuration/authorization-and-permission-request/</link><description>Recent content in Authorization &amp; Permission Request on Virtosoftware Guides &amp; Docs</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 12 Mar 2026 09:41:46 +0000</lastBuildDate><atom:link href="https://docs-hugo-4dl.pages.dev/docs/calendar-overlay-pro/installation-and-configuration/authorization-and-permission-request/index.xml" rel="self" type="application/rss+xml"/><item><title>EWS.Permission Deprecation Notice and Virto Calendar Compatibility</title><link>https://docs-hugo-4dl.pages.dev/docs/calendar-overlay-pro/installation-and-configuration/authorization-and-permission-request/ews-permission-deprecation-notice-and-virto-calendar-compatibility/</link><pubDate>Mon, 09 Feb 2026 13:40:30 +0000</pubDate><guid>https://docs-hugo-4dl.pages.dev/docs/calendar-overlay-pro/installation-and-configuration/authorization-and-permission-request/ews-permission-deprecation-notice-and-virto-calendar-compatibility/</guid><description>&lt;h2 id="context"&gt;Context&lt;a class="anchor" href="#context"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Microsoft is deprecating certain Exchange Web Services (EWS) API permissions, including the &lt;code&gt;EWS.AccessAsUser.All&lt;/code&gt; scope, in favor of the newer Microsoft Graph API permissions (e.g., &lt;code&gt;Mail.ReadWrite&lt;/code&gt;, &lt;code&gt;Calendars.ReadWrite&lt;/code&gt;). As part of their ongoing modernization efforts, some administrators may receive alerts from Microsoft regarding applications still using EWS-based permissions.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://pub-a28a5107f8a14f3d8a0272bc4e8c6b62.r2.dev/wp-content/uploads/2026/02/Screenshot-2026-02-09-at-14.47.18-1024x640.png" alt="" /&gt;&lt;/p&gt;
&lt;h2 id="explanation"&gt;Explanation&lt;a class="anchor" href="#explanation"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Virto Calendar primarily integrates with &lt;strong&gt;Microsoft 365&lt;/strong&gt; through the &lt;strong&gt;Microsoft Graph API&lt;/strong&gt;, which serves as the main interface for all calendar operations—such as viewing events, creating meetings, and managing user and group calendars.&lt;/p&gt;</description></item><item><title>Virto Apps</title><link>https://docs-hugo-4dl.pages.dev/docs/calendar-overlay-pro/installation-and-configuration/authorization-and-permission-request/virto-apps/</link><pubDate>Thu, 12 Mar 2026 09:41:46 +0000</pubDate><guid>https://docs-hugo-4dl.pages.dev/docs/calendar-overlay-pro/installation-and-configuration/authorization-and-permission-request/virto-apps/</guid><description>&lt;p&gt;A Global Administrator can manage the Virto Apps (Virto Authorization App) via the Azure Active Directory portal at &lt;a href="https://portal.azure.com/"&gt;&lt;strong&gt;https://portal.azure.com/&lt;/strong&gt;&lt;/a&gt;. You can locate it by navigating to &lt;strong&gt;Azure Active Directory =&amp;gt; Enterprise application =&amp;gt; Virto Apps&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;This application is necessary for using VirtoSoftware apps in SharePoint, synchronizing them with Outlook, Planner, and other Microsoft products, and inheriting permissions configured by the global administrator for users across various Microsoft ecosystem applications.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Delegated permissions&lt;/strong&gt; are used when an application acts on a user’s behalf. They allow the application to access only what the user themselves can access. For instance, if an application is granted delegated permission to read files on behalf of a user named Alex, it can only read the files that Alex has access to. &lt;strong&gt;Important&lt;/strong&gt;: in &lt;a href="https://learn.microsoft.com/en-us/azure/active-directory/develop/delegated-access-primer"&gt;delegated access&lt;/a&gt;, both your client app and the signed-in user must be authorized correctly. Simply granting a scope is not sufficient. If the client app lacks the necessary scope or the user lacks sufficient rights to read or modify the resource, the call will fail.&lt;/p&gt;</description></item></channel></rss>