<?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 Subhagya on Medium]]></title>
        <description><![CDATA[Stories by Subhagya on Medium]]></description>
        <link>https://medium.com/@subhagya88?source=rss-c8630546e127------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*i5WWttsAGtm3mXKa.jpg</url>
            <title>Stories by Subhagya on Medium</title>
            <link>https://medium.com/@subhagya88?source=rss-c8630546e127------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 07:47:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@subhagya88/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[Understanding Licensing, Guest Access and the Right Use Cases]]></title>
            <link>https://medium.com/@subhagya88/understanding-licensing-guest-access-and-the-right-use-cases-d618838e03cd?source=rss-c8630546e127------2</link>
            <guid isPermaLink="false">https://medium.com/p/d618838e03cd</guid>
            <category><![CDATA[power-pages]]></category>
            <category><![CDATA[power-apps-vs-power-pages]]></category>
            <category><![CDATA[powerapps]]></category>
            <category><![CDATA[power-platform-licensing]]></category>
            <category><![CDATA[powerapps-developers]]></category>
            <dc:creator><![CDATA[Subhagya]]></dc:creator>
            <pubDate>Mon, 16 Feb 2026 19:31:05 GMT</pubDate>
            <atom:updated>2026-02-16T19:31:05.091Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0XXNUCl99LxAP5sVaon6tw.jpeg" /></figure><p>Microsoft Power Platform gives organizations powerful tools to build apps, automate processes and create scalable digital experiences. But one area many teams still find confusing is the difference between <strong>Power Apps</strong> and <strong>Power Pages</strong>, especially when it comes to <strong>external users</strong> and <strong>guest access</strong>.</p><p>This article explains the differences clearly with practical examples, licensing rules and common scenarios to help you choose the right tool.</p><h3>🔵 What Is Power Apps?</h3><p>Power Apps is designed to build <strong>internal business applications</strong> for employees within your organization. These include</p><ul><li>Canvas apps</li><li>Model-driven apps</li><li>Internal tools for workflows, approvals, data entry, and operations</li></ul><h3>When Power Apps is ideal</h3><ul><li>HR on-boarding apps</li><li>Internal dashboards</li><li>Inventory tools</li><li>RPA support apps</li><li>Data entry forms for internal teams</li></ul><h3>Licensing for internal users</h3><p>Internal users typically have Microsoft 365. but,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/835/1*KGVb9Cvi24FaY2pnoewBQA.png" /></figure><p>So internal staff may not need extra licensing unless your app uses premium services.</p><h3><strong>What About Guest Users in Power Apps?</strong></h3><p>This is where people get confused.</p><p>Yes, you <em>can</em> add external people as <strong>Azure AD B2B guest users</strong> and share Power Apps with them.</p><p>But,</p><h4>⚠️ Guest users ALWAYS require a Power Apps license</h4><p>Even if your internal users don’t.</p><p>Why?<br> Guest users do <strong>not</strong> receive any usage rights from your Microsoft 365 licenses. They are treated as external entities who must be individually licensed.</p><p>This makes Power Apps <strong>unsuitable for large numbers of external users</strong>.</p><h3>Good for</h3><ul><li>A small vendor team (3–5 people)</li><li>One consultant working with your internal team</li></ul><h3>Not good for</h3><ul><li>Hundreds of customers</li><li>Public users</li><li>Community portals</li></ul><p>For that, you need Power Pages.</p><h4><strong>What Is Power Pages?</strong></h4><p>Power Pages allows you to create external-facing websites that are secure, scalable, and accessible to anyone public or authenticated.</p><p>Examples</p><ul><li>Customer service portals</li><li>Vendor onboarding sites</li><li>Appointment booking systems</li><li>Public dashboards</li><li>Citizen self-service portals</li></ul><h3>✔ Licensing Model</h3><p>Power Pages is <strong>not licensed per user</strong>.Instead, it’s based on</p><ul><li><strong>Authenticated sessions</strong> (user logs in)</li><li><strong>Anonymous sessions</strong> (public access)</li></ul><p>This makes it dramatically more cost-effective for external audiences.</p><h3>Power Apps vs Power Pages: The Real Difference</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PNW1T53OWSKV4p-_LKKsmA.png" /></figure><h3>A Simple Rule of Thumb</h3><h4>✔ Use Power Apps</h4><p>For internal business applications used by people inside your organization.</p><h4>✔ Use Power Pages</h4><p>When external users need to interact with your data or processes — especially at scale.</p><h3>Real-World Example</h3><h4>Scenario 1: Vendor submitting monthly financial reports</h4><ul><li>2–3 vendor staff</li><li>Internal employees approve reports<br>Power Apps could work. But each vendor user must have a Power Apps license.</li></ul><h4>Scenario 2: 800 customers submitting service requests</h4><p>Power Pages is the only practical choice</p><ul><li>No per-user licensing</li><li>Built-in secure authentication</li><li>Lower cost and higher scalability</li></ul><h3>Conclusion</h3><p>Power Apps and Power Pages solve two different problems</p><ul><li><strong>Power Apps → Internal Apps</strong></li><li><strong>Power Pages → External Portals</strong></li></ul><p>You <em>can</em> use Power Apps with guest users, but you should only do this for <strong>a very small number of external collaborators</strong>. For any public-facing or customer-facing solution, Power Pages is the clear winner in both functionality and cost.</p><p>Understanding these differences helps prevent licensing surprises, improves architecture decisions, and ensures your Power Platform solutions scale effectively.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d618838e03cd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Power Automate Admin Tip: Access Any Flow Using PowerShell]]></title>
            <link>https://medium.com/@subhagya88/power-automate-admin-tip-access-any-flow-using-powershell-bf1d06932cd5?source=rss-c8630546e127------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf1d06932cd5</guid>
            <dc:creator><![CDATA[Subhagya]]></dc:creator>
            <pubDate>Wed, 02 Apr 2025 18:18:35 GMT</pubDate>
            <atom:updated>2025-04-02T18:22:23.447Z</atom:updated>
            <content:encoded><![CDATA[<p>As a Power Platform Admin, I assumed I’d have full access to everything inside our environment, including flows created by other users. I was wrong.</p><p>Recently, I ran into a situation where I needed to view and edit a cloud flow created by a colleague. Unfortunately, I was hit with this lovely message</p><blockquote>“<strong>You do not have permission to view this flow.</strong>”</blockquote><p>Even as an admin, Power Automate restricts access to flows unless you’re added as a co-owner. But after a bit of PowerShell wrangling, I successfully granted myself edit access. here’s how you can do the same.</p><h3>Prerequisites</h3><p>You’ll need</p><ul><li>Power Platform Admin rights</li><li>PowerShell 5.1+</li><li><a href="https://learn.microsoft.com/en-us/powershell/powerapps/overview">Power Platform PowerShell modules</a></li></ul><h3>1. Install the Required PowerShell Modules</h3><p><strong>Open PowerShell and run the following command</strong></p><p>Install-Module -Name Microsoft.PowerApps.Administration.PowerShell -Force -AllowClobber -Scope CurrentUser<br>Install-Module -Name Microsoft.PowerApps.PowerShell -Force -AllowClobber -Scope CurrentUser</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GGwhbRwUTOgo-mSNKLR3Iw.png" /></figure><p><strong>Then, import the modules</strong></p><p>Import-Module Microsoft.PowerApps.Administration.PowerShell<br>Import-Module Microsoft.PowerApps.PowerShell</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HfUPnlWwL-dV-VdoOzAHfA.png" /></figure><h3>2. Log In</h3><p><strong>Add power apps account</strong></p><p>Add-PowerAppsAccount</p><p>A pop-up will prompt you to log in with your admin account.</p><h3>3. Get the Environment Name</h3><p><strong>Friendly environment names won&#39;t work due to special characters. Use this to get the actual environment name</strong></p><p>Get-AdminPowerAppEnvironment | Select-Object DisplayName, EnvironmentName</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YX-iW_abwR8-OsBqboCR-w.png" /></figure><p>Look for the correct environment and copy the EnvironmentName (e.g : Default-xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).</p><h3>4. Get the Flow ID (FlowName)</h3><p><strong>If you know the flow creator’s email</strong></p><p>Get-AdminFlow -UserId “<a href="/service/mailto:user@domain.com">user@domain.com</a>”</p><p><strong>Or to list all flows</strong></p><p>Get-AdminFlow</p><p>Find the flow you want and copy the <strong>FlowName</strong> (it will look like a GUID).</p><h3>5. Get Your Azure AD Object ID</h3><p><strong>To find your </strong><strong>PrincipalObjectId</strong></p><p>Get-AdminUser | Where-Object {$_.UserPrincipalName -eq “<a href="/service/mailto:your.email@domain.com">your.email@domain.com</a>”}</p><h3>6. Add Yourself as Co-Owner</h3><p><strong>Now run the command below with the values you gathered</strong></p><p>Set-AdminFlowOwnerRole \<br> -EnvironmentName “&lt;your-environment-name&gt;” \<br> -FlowName “&lt;your-flow-id&gt;” \<br> -PrincipalObjectId &lt;your-AAD-object-id&gt; \<br> -PrincipalType User \<br> -RoleName CanEdit</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*EqOeTl5RGsc_mK52aXpdCA.png" /></figure><p>If successful, you’ll see a 200 OK response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G7S9BYrwHVGix-3WNeMglg.png" /></figure><p>This approach saved me when I needed to access a flow without waiting on the original owner. If you’re a Power Platform admin, this trick gives you full control over orphaned or inaccessible flows.</p><p><strong>Recommendation </strong>: Always build flows inside <strong>Solutions</strong> for easier role management and handovers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf1d06932cd5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Successfully Introduce a New RPA Tool in Your Organization]]></title>
            <link>https://medium.com/@subhagya88/how-to-successfully-introduce-a-new-rpa-tool-in-your-organization-eaeeb093afb6?source=rss-c8630546e127------2</link>
            <guid isPermaLink="false">https://medium.com/p/eaeeb093afb6</guid>
            <dc:creator><![CDATA[Subhagya]]></dc:creator>
            <pubDate>Sat, 22 Mar 2025 18:03:18 GMT</pubDate>
            <atom:updated>2025-03-22T18:05:53.033Z</atom:updated>
            <content:encoded><![CDATA[<p>Robotic Process Automation (RPA) is no longer a buzzword. it’s a necessity for organizations seeking efficiency, scalability, and digital resilience. However, bringing a new RPA tool into your organization isn’t just a technical decision. it’s a strategic move that requires vision, planning, and organizational alignment. In this article, we’ll walk through a comprehensive roadmap to successfully introduce a new RPA tool into your company from setting the right vision to driving adoption and long-term scale.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oYUQGo6uSqiR1WqwTFaLAQ.png" /></figure><p><strong>1. Define the Vision</strong></p><p>Before selecting a tool, define what success looks like. Is your goal to reduce manual workload? Improve compliance? Drive innovation? Your vision should</p><ul><li>Align with organizational goals (cost savings, error reduction, faster turnaround times)</li><li>Inspire buy in from leadership and business units</li><li>Look beyond the tool focus on building an automation-first mindset</li><li>Envision a future where automation empowers teams, not replaces them</li></ul><p><strong>2. Assess the Current Landscape</strong></p><p>Understand where you stand before planning where to go.</p><ul><li>Inventory existing tools and automation efforts</li><li>Evaluate processes suitable for automation</li><li>Assess team readiness (skills, infrastructure, mindset)</li><li>Identify challenges in current workflows that RPA could solve</li></ul><p><strong>3. Select the Right Tool</strong></p><p>Choose a tool that fits your organization’s unique needs.</p><ul><li>Consider usability for both developers and business users (citizen developers)</li><li>Evaluate scalability, licensing, integration capabilities, and vendor support</li><li>Conduct Proof of Concepts (PoCs) with shortlisted tools</li><li>Gather feedback from both IT and business teams during the selection process</li></ul><p><strong>4. Develop a Governance Framework</strong></p><p>Governance is key to sustainable success.</p><ul><li>Define clear roles and responsibilities ( RPA CoE, business analysts, developers)</li><li>Set up development best practices and standards</li><li>Establish access controls, security policies, and compliance guidelines</li><li>Design a process for pipeline management and prioritization</li></ul><p><strong>5. Start Small, Win Big</strong></p><p>Begin with a high-impact but low-complexity process.</p><ul><li>Deliver value quickly and build organizational confidence</li><li>Use early success stories to gain momentum</li><li>Demonstrate ROI through metrics such as time saved, error reduction, or employee satisfaction</li></ul><p><strong>6. Training and Change Management</strong></p><p>Even the best tool fails without proper change management.</p><ul><li>Upskill your teams with training programs for both IT and business users</li><li>Establish internal RPA champions and communities of practice</li><li>Communicate wins and encourage cross-team collaboration</li><li>Embed automation into your organization’s culture</li></ul><p><strong>7. Measure, Improve, and Scale</strong></p><p>Keep improving as you grow.</p><ul><li>Set KPIs to measure success and gather feedback regularly</li><li>Establish a feedback loop between developers, users, and leadership</li><li>Continuously iterate on your framework and processes</li><li>Scale based on a clear roadmap and automation maturity model</li></ul><p><strong>Conclusion</strong></p><p>Introducing a new RPA tool is more than a technology upgrade. it’s a catalyst for organizational transformation. By starting with a strong vision,selecting the right tool, building solid governance, and focusing on people, you can drive lasting success. The journey is continuous but with the right foundation, your organization can unlock the full potential of automation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eaeeb093afb6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New Dataverse Enhancements and AI-Powered Productivity with Microsoft 365 Copilot]]></title>
            <link>https://medium.com/@subhagya88/new-dataverse-enhancements-and-ai-powered-productivity-with-microsoft-365-copilot-45de9ff93b99?source=rss-c8630546e127------2</link>
            <guid isPermaLink="false">https://medium.com/p/45de9ff93b99</guid>
            <dc:creator><![CDATA[Subhagya]]></dc:creator>
            <pubDate>Sat, 01 Jun 2024 03:26:16 GMT</pubDate>
            <atom:updated>2024-06-01T03:26:16.660Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*nOm1o-SXw0aX69sKpBM7qg.png" /></figure><p>Microsoft’s recent enhancements on data management such as Dataverse and the introduction of AI-powered productivity tools with Microsoft 365 Copilot are significant tools for both IT professionals and business users alike. These innovations can play major role in transforming how we interact with data and automating routine tasks, allowing us to focus on strategic, value-added activities.</p><p><strong>What is Microsoft Dataverse?</strong></p><p>Microsoft Dataverse, previously known as the Common Data Service (CDS), is a cloud-based storage solution that allows businesses to securely store and manage data used by business applications. Dataverse is part of the Power Platform and provides a unified data schema, making it easier to connect data across various Microsoft applications like Dynamics 365, Power BI, Power Automate, Power Apps, and more.</p><p><strong>Evolution of Dataverse</strong></p><ol><li><strong>Common Data Service (CDS)</strong>: Initially, it was introduced as CDS to provide a robust data storage solution for PowerApps and Dynamics 365. Users could easily use this instead of connecting another data storage solution.</li><li><strong>Introduction of Dataflex</strong>: For a brief period, Microsoft rebranded CDS as Dataflex, aiming to simplify data integration for business applications.</li><li><strong>Rebranding to Dataverse</strong>: Eventually, it was rebranded to Dataverse, incorporating enhanced features and deeper integration with the Power Platform and Microsoft 365 ecosystem. Unlike a conventional database, Microsoft database is equipped with many inbuilt functionalities such as integrated data analytics and AI builders.</li></ol><p><strong>Differences with Other Databases</strong></p><ol><li><strong>Unified Data Schema</strong>: Unlike traditional databases, Dataverse uses a common data model to standardize data, ensuring consistency across applications.</li><li><strong>Seamless Integration</strong>: Dataverse offers integration with Microsoft tools and third-party applications, making it easier to create unified workflows.</li><li><strong>Security and Compliance</strong>: Built-in security features, including role-based access control and data encryption, ensure that sensitive data is protected.</li><li><strong>Low-Code/No-Code Environment</strong>: Dataverse is designed for use in low-code and no-code environments, empowering business users with minimal programming skills to create comprehensive and stable applications.</li></ol><p><strong>Capabilities and Limitations</strong></p><p><strong>Capabilities</strong></p><ul><li><strong>Scalability</strong>: Dataverse can handle large volumes of data, supporting enterprise-level applications.</li><li><strong>Data Management</strong>: Advanced data management features, such as data import/export, data validation, and relationship management.</li><li><strong>AI and Analytics</strong>: Integration with AI Builder and Power BI for advanced analytics and AI-driven insights.</li></ul><p><strong>Limitations</strong></p><ul><li><strong>Customization Complexity</strong>: While it’s designed for low-code environments, complex customizations may still require developer intervention.</li><li><strong>Performance for Large-Scale Operations</strong>: when equipped with extremely large datasets or high transaction volumes it may be necessary to optimize the performance as required.</li><li><strong>Cost</strong>: Dataverse can be more expensive compared to other database solutions, especially for extensive use cases.</li></ul><p><strong>Enhanced Capabilities</strong></p><ol><li><strong>Improved Data Integration</strong>: New connectors and APIs make it easier to integrate Dataverse with a range of external systems, ensuring seamless data flow and more comprehensive insights.</li><li><strong>Enhanced Security</strong>: With strong encryption and advanced access controls, Dataverse now offers sophisticated protection for sensitive data, meeting the strict security requirements of modern enterprises.</li><li><strong>Scalability and Performance</strong>: Optimizations in data storage and processing ensure that Dataverse can handle larger volumes of data with increased efficiency, supporting the growth and scalability needs of businesses.</li></ol><p><strong>AI-Powered Productivity with Microsoft 365 Copilot</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/558/1*rfpV6J4t29H9-A911qmVkg.png" /></figure><p>Microsoft 365 Copilot introduces the power of AI for easing up everyday tasks, helping users to work smart and efficiently. This new tool leverages advanced machine learning algorithms to provide intelligent assistance across Microsoft 365 applications, including Word, Excel, PowerPoint, and Outlook.</p><p><strong>Key Features of Microsoft 365 Copilot</strong></p><ol><li><strong>Context-Aware Assistance</strong>: Copilot can understand the context of your work, providing personalized suggestions and support automation of routine tasks. For instance, it can draft emails, generate reports, and even create presentations based on minimal input.</li><li><strong>Natural Language Processing (NLP)</strong>: Users can interact with Copilot using natural language commands, making it easy to perform complex tasks without needing to master advanced software features.</li><li><strong>Integration with Dataverse</strong>: By connecting with Dataverse, Copilot can access and utilize business data to provide more accurate and personalized assistance, enhancing decision-making and operational efficiency.</li></ol><p><strong>Real-World Applications</strong></p><p>The combination of enhanced Dataverse capabilities and Microsoft 365 Copilot creates a world of opportunities for businesses. Here are a few areas how these innovations can be applied</p><ol><li><strong>Automated Reporting</strong>: By leveraging Copilot’s AI capabilities, users can automate the generation of detailed reports using data from Dataverse. This not only saves time but also ensures consistency and accuracy in reporting.</li><li><strong>Streamlined Customer Service</strong>: Integrating Dataverse with customer service platforms allows real-time access to customer data, enabling more personalized and efficient service delivery. Copilot can assist by suggesting responses and automating follow-up actions.</li><li><strong>Data-Driven Decision Making</strong>: Enhanced data integration and processing capabilities in Dataverse enable businesses to gather comprehensive insights from various sources. Coupled with Copilot’s ability to analyze and present this data, decision-makers can make more informed and strategic choices.</li></ol><p><strong>Dynamics 365 and Microsoft Fabric</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/905/1*XJziW6Uez6kfJqWRMXuugw.png" /></figure><p>In the current context of competitive world, organizations seek to make better decisions based on data. Dataverse integrates Dynamics 365 business application data and Microsoft tools resulting in actionable insights and reporting, like the Dataverse Power Query connector, rich Dataverse integrations with Power BI, and Azure Synapse Link for Dataverse.</p><p>As a latest addition, Microsoft announced Microsoft Fabric, a new, end-to-end analytics platform. It integrates Data Factory, Data Engineering, Data Warehousing, Real-Time Analytics, Data Science, Data Activator, and Power BI into a unified lake-centric SaaS solution. This simplifies data management, ensuring a single source of truth, and makes business data more accessible for better decision-making. Using these novel tools and with just a single click, you will get more insights about your business data stored in Dataverse.</p><p><strong>Eliminate Data Silos with Fabric and Dynamics 365</strong></p><p>Microsoft Fabric’s lake-centric approach helps to eliminate data silos. Combine data from your applications and devices, websites, mobile apps, sensors, and signals from your warehouse and factories with data from your business processes in Dynamics 365 sales, cases, inventory, and orders to predict potential delays or shortages that might potentially affect keeping your promises to customers.</p><p>Direct integration between Dataverse and Microsoft Fabric saves significant time and effort. Your makers can build low-code apps and automations to orchestrate business processes and react to insights found in Microsoft Fabric using connectors to over 1,000 apps. Add those insights back to Dataverse as external or virtual tables through the SQL endpoint, and makers can turn them into low-code apps with Power Apps, Power Pages, or Power Automate using skills they already have.</p><p><strong>Optimize Capacity Costs with Long-Term Retention Policies in Dataverse</strong></p><p>The longer an enterprise application runs, the more historical data it accumulates. Customers often need to retain data for compliance and regulatory reasons, but storage costs can escalate. With the new long-term retention capability in Microsoft Dataverse, you can save on storing inactive data that’s rarely accessed without investing in custom archival solutions.</p><p>From the Power Apps maker portal, admins can set retention policies with criteria driven by compliance requirements and manage the policies with a dashboard. The retained data has security controls and governance applied and never leaves the Dataverse environment. Admins can access it when needed using advanced find. No new data or security model is required, even if you customize the application or Dataverse tables later.</p><p><strong>New Zero-Trust Security Features in Dataverse</strong></p><p>The foundation of any enterprise-grade solution is security. Dataverse enables even more sophisticated security features in Dynamics 365 and Power Platform with new IP access management and managed encryption key features.</p><p><strong>IP Enforcement</strong>:</p><ul><li><strong>IP Restrictions</strong>: Azure AD access evaluation restricts unauthorized access based on IP address by evaluating user-critical events like account deletion. When changes that require restriction of user access occur, access is denied in near-real-time.</li><li><strong>IP Firewall</strong>: Azure AD puts valuable business data behind an IP firewall, restricting user access if the IP address is not a part of a trusted network. Threats like insider data exfiltration or token replay attacks can be mitigated for all business processes running in Dataverse.</li></ul><p><strong>Encryption Keys</strong>: In addition to improving granular security access, Dataverse safeguards sensitive customer data by integrating Azure Key Vault customer-managed encryption keys in Dataverse environments. Organizations can create a Power Platform enterprise policy that can be applied to individual or groups of Dynamics 365 and Power Platform environments across storage types like analytics, logs, and more.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45de9ff93b99" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>