<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Subramanian PR on Medium]]></title>
        <description><![CDATA[Stories by Subramanian PR on Medium]]></description>
        <link>https://medium.com/@superminion?source=rss-b411f03c8479------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*XlSz4SF59fxYMoJ7hSsrGQ.jpeg</url>
            <title>Stories by Subramanian PR on Medium</title>
            <link>https://medium.com/@superminion?source=rss-b411f03c8479------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:51:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@superminion/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Did You Know You Can Copy an Azure Incremental Snapshot to Another Region?]]></title>
            <link>https://superminion.medium.com/did-you-know-you-can-copy-an-azure-incremental-snapshot-to-another-region-008d11ecb9d9?source=rss-b411f03c8479------2</link>
            <guid isPermaLink="false">https://medium.com/p/008d11ecb9d9</guid>
            <category><![CDATA[azure-virtual-machines]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[microsoft-azure]]></category>
            <dc:creator><![CDATA[Subramanian PR]]></dc:creator>
            <pubDate>Sat, 26 Sep 2026 20:35:12 GMT</pubDate>
            <atom:updated>2026-09-26T20:35:12.450Z</atom:updated>
            <content:encoded><![CDATA[<p>A simple way to move Azure managed disks across regions without using Azure Site Recovery</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bSC-a_thoxs5QFypp2a-qQ.png" /></figure><h3>Why This Matters</h3><p>When we think about moving data between Azure regions, services such as <strong>Azure Site Recovery (ASR)</strong> and <strong>Azure Migrate</strong> usually come to mind.</p><p>But there is another capability that is surprisingly useful and easy to overlook:</p><blockquote><strong><em>Azure allows you to copy incremental snapshots of managed disks directly to another Azure region.</em></strong></blockquote><p>This can be particularly useful when you don’t need continuous replication or a complete disaster-recovery solution.</p><h3>The Problem</h3><p>Suppose you have a VM running in Central India with a large data disk.</p><p>You want to make that disk available in South India.</p><p>The first solution that may come to mind is Azure Site Recovery.</p><p>When you create a <strong>Full</strong> snapshot, the <strong>Copy snapshot</strong> workflow doesn’t provide the same cross-region capability.</p><h3>Understanding the Solution</h3><h4>What is an incremental snapshot?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pPITjvU_7bCJuYz32UkDAw.png" /><figcaption>cross-region-snapshot</figcaption></figure><p>An incremental snapshot is a point-in-time backup of an Azure managed disk.</p><p>The important part is how Azure stores successive snapshots.</p><p>Suppose your disk is <strong>512 GiB</strong>.</p><p>The first incremental snapshot is a <strong>full copy of the disk</strong>. Now suppose some data changes.The second snapshot stores only the changes since the previous snapshot. For the third the same concept continues.</p><p>When you create a managed disk from an incremental snapshot, Azure reconstructs the full disk corresponding to that point in time.</p><h3>Implementation Overview</h3><p>Let’s look at the practical workflow.</p><h4>Step 1 — Create an incremental snapshot</h4><p>From the Azure Portal:</p><p><strong>Azure Portal &gt; Managed Disks &gt; Select your data disk → Create snapshot</strong></p><p>When creating the snapshot, select:</p><p><strong>Snapshot type &gt; Incremental</strong></p><h4>Step 2 — Open the snapshot</h4><p>Go to:</p><p><strong>Azure Portal &gt; Snapshots &gt; Your incremental snapshot &gt; Copy snapshot</strong></p><h4>Step 3 — Copy the incremental snapshot to another region</h4><p>Select: <strong>Copy snapshot</strong></p><p>You can then create the destination snapshot in the target region.</p><h4>Step 4 — Wait for the snapshot copy</h4><p>Immediately after starting the copy, don’t expect the destination snapshot to be ready.</p><p>The target snapshot can initially show Snapshot access state: Pending</p><p>his is normal while Azure is processing the copy.</p><p>You should wait until the copy has completed and the snapshot becomes available for restore/use.</p><h4>Step 5 — Create the managed disk in the target region</h4><p>Once the copied snapshot is available:</p><p><strong>Snapshot &gt; Create disk</strong></p><p>Configure the new managed disk according to your requirements.</p><h4>6. Conclusion</h4><p>Azure has a useful capability that can easily be overlooked:</p><blockquote><strong><em>Incremental managed-disk snapshots can be copied directly to another Azure region.</em></strong></blockquote><p>The most important detail is that <strong>the first incremental snapshot is a full copy of the disk</strong>, while subsequent incremental snapshots capture only the changes since the previous snapshot. Azure can reconstruct the complete disk state when you create a disk from the snapshot.</p><p>So the next time you need to move or copy an Azure managed data disk between regions, don’t immediately assume you need ASR.</p><h3>Official References</h3><p>Here are the Microsoft Learn references I would include at the end of the Medium article:</p><ul><li><a href="https://learn.microsoft.com/en-us/azure/virtual-machines/disks-copy-incremental-snapshot-across-regions?tabs=azure-cli">Copy an incremental snapshot to a new region — Microsoft Learn</a></li><li><a href="https://learn.microsoft.com/en-us/azure/virtual-machines/disks-incremental-snapshots?tabs=azure-cli">Create an incremental snapshot for managed disks — Microsoft Learn</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=008d11ecb9d9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Restricting Microsoft Graph Mail.Send]]></title>
            <link>https://superminion.medium.com/restricting-microsoft-graph-mail-send-97641641eeff?source=rss-b411f03c8479------2</link>
            <guid isPermaLink="false">https://medium.com/p/97641641eeff</guid>
            <category><![CDATA[exchange-online]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[azure-cloud]]></category>
            <category><![CDATA[microsoft-graph-api]]></category>
            <dc:creator><![CDATA[Subramanian PR]]></dc:creator>
            <pubDate>Sun, 05 Jul 2026 08:45:22 GMT</pubDate>
            <atom:updated>2026-07-05T08:45:22.450Z</atom:updated>
            <content:encoded><![CDATA[<h3>Restricting Microsoft Graph Mail.Send to Specific Mailboxes Using Exchange Online Application Access Policies</h3><p><em>Learn how to secure Microsoft Graph applications by limiting </em><strong><em>Mail.Send (Application)</em></strong><em> permissions to only approved mailboxes using Exchange Online Application Access Policies.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R2jFuh7MVf_w1ThtSn8bWg.png" /></figure><h3>Introduction</h3><p>Microsoft Graph has become the preferred API for integrating applications with Microsoft 365 services. Whether you’re building notification systems, scheduled jobs, or enterprise workflows, <strong>Mail.Send (Application)</strong> enables applications to send emails without requiring a signed-in user.</p><p>While this simplifies automation, it also introduces an important security consideration. By default, an application with <strong>Mail.Send (Application)</strong> permission can send emails as any mailbox in the Microsoft 365 tenant.</p><p>In this article, we’ll explore how <strong>Exchange Online Application Access Policies</strong> help enforce the principle of least privilege by restricting applications to only approved mailboxes.</p><h3>Why It Matters Now</h3><p>Many applications relied on SMTP with Basic Authentication or legacy Exchange protocols to send emails. To improve security and reduce credential-based attacks, Microsoft has retired <strong>Basic Authentication</strong> for most Exchange Online protocols and encourages organizations to adopt <strong>Modern Authentication (OAuth 2.0)</strong>.</p><p>For email-sending applications, organizations now have three common options:</p><ul><li><strong>Microsoft Graph API </strong>— Best for cloud-native applications integrating with Microsoft 365.</li><li><strong>SMTP AUTH with OAuth 2.0</strong> — Suitable for applications that still require SMTP.</li><li><strong>SMTP Relay</strong> — Commonly used by legacy applications, printers, and network devices that cannot support OAuth.</li></ul><p>While Microsoft Graph is the recommended approach, granting an application the <strong>Mail.Send (Application)</strong> permission gives it broad access by default. Without additional restrictions, the application can send emails as any mailbox in the tenant.</p><p>This is where <strong>Exchange Online Application Access Policies</strong> become an essential security control.</p><h3>The Problem</h3><p>Imagine you’ve built an application that sends automated notification emails from a shared mailbox such as:</p><pre>notifications@contoso.com</pre><p>The application only needs to send emails from this mailbox.</p><p>Without additional restrictions, the same application could also send emails from:</p><ul><li><a href="/service/mailto:finance@contoso.com">finance@contoso.com</a></li><li><a href="/service/mailto:hr@contoso.com">hr@contoso.com</a></li><li><a href="/service/mailto:ceo@contoso.com">ceo@contoso.com</a></li></ul><p>Even though the application never intends to use those mailboxes, the permission technically allows it.</p><p>For organizations with strict security and compliance requirements, that’s a significant risk.</p><h3>The Solution: Application Access Policies</h3><p>Exchange Online Application Access Policies let you scope Microsoft Graph application permissions to a defined group of mailboxes.</p><p>The approach is straightforward:</p><ol><li>Create a <strong>mail-enabled security group</strong>.</li><li>Add the approved mailboxes to the group.</li><li>Create an Application Access Policy for your Microsoft Entra application.</li><li>Test the policy to confirm only authorized mailboxes are accessible.</li></ol><p>This provides an additional layer of security without changing your application’s authentication flow.</p><h3>Useful PowerShell Commands</h3><p>Create a Mail-Enabled Security Group</p><pre>New-DistributionGroup `<br>-Name &quot;Graph-MailSend-Restricted&quot; `<br>-PrimarySmtpAddress graph-mailsend-restricted@contoso.com `<br>-Type Security</pre><p>Add Approved Mailboxes to the Security Group</p><pre>Add-DistributionGroupMember `<br>-Identity &quot;Graph-MailSend-Restricted&quot; `<br>-Member notifications@contoso.com</pre><p>Create the Application Access Policy:</p><pre>New-ApplicationAccessPolicy `<br>-AppId &quot;&lt;Application-Client-ID&gt;&quot; `<br>-PolicyScopeGroupId &quot;&lt;MailEnabledSecurityGroup&gt;&quot; `<br>-AccessRight RestrictAccess</pre><p>Verify the policy:</p><pre>Get-ApplicationAccessPolicy |<br>Where-Object {$_.AppId -eq &quot;xxxxxxxx-xxxx-xxxxxxxxxxxxxxxx&quot;}</pre><p>Test access:</p><pre>Test-ApplicationAccessPolicy `<br>-AppId &quot;&lt;Application-Client-ID&gt;&quot; `<br>-Identity notifications@contoso.com</pre><p><em>If the application attempts to send mail from an unauthorized mailbox, Microsoft Graph returns an authorization error instead of sending the message.</em></p><h3>Common Issues</h3><p>During testing, you may encounter a few common issues:</p><ul><li><strong>Policy changes aren’t immediately effective.</strong> Allow time for Exchange Online to propagate the changes before retesting.</li><li><strong>Cached access tokens.</strong> Request a new OAuth token after updating the policy.</li><li><strong>Incorrect group membership.</strong> Ensure the mailbox is part of the mail-enabled security group.</li></ul><p><strong><em>Note:</em></strong><em> Microsoft has introduced </em><strong><em>Exchange Online RBAC for Applications</em></strong><em> as the long-term replacement for </em><strong><em>Application Access Policies</em></strong><em>. Existing environments continue to use Application Access Policies, but new implementations should evaluate the RBAC for Applications model as recommended by Microsoft.</em></p><p><a href="https://learn.microsoft.com/en-us/exchange/permissions-exo/application-rbac">Role Based Access Control for Applications in Exchange Online</a></p><h3>References</h3><p>The following Microsoft Learn articles provide additional guidance on Microsoft Graph permissions and Exchange Online Application Access Policies:</p><ul><li><a href="https://learn.microsoft.com/en-us/exchange/permissions-exo/application-access-policies">Application Access Policies (legacy)</a></li><li><a href="https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/new-applicationaccesspolicy?view=exchange-ps">New-ApplicationAccessPolicy (ExchangePowerShell)</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97641641eeff" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>