<?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 Jere Vekka on Medium]]></title>
        <description><![CDATA[Stories by Jere Vekka on Medium]]></description>
        <link>https://medium.com/@jerevekka?source=rss-e0a688b76a8d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*l_myKq124Ga2bCJF.</url>
            <title>Stories by Jere Vekka on Medium</title>
            <link>https://medium.com/@jerevekka?source=rss-e0a688b76a8d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:05:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jerevekka/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[Securing Power Platform: Disabling Guest Access at Scale]]></title>
            <link>https://medium.com/@jerevekka/securing-power-platform-disabling-guest-access-at-scale-04df838e1281?source=rss-e0a688b76a8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/04df838e1281</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[powerplatform]]></category>
            <category><![CDATA[microsoft-power-platform]]></category>
            <dc:creator><![CDATA[Jere Vekka]]></dc:creator>
            <pubDate>Thu, 16 Oct 2025 06:40:55 GMT</pubDate>
            <atom:updated>2025-10-16T06:40:55.983Z</atom:updated>
            <content:encoded><![CDATA[<p>As part of our ongoing effort to secure our Power Platform tenant and environments, we recently explored a tool called <strong>power-pwn</strong>. This open-source project demonstrates several attack vectors against Power Platform, and one particular scenario caught my attention — a YouTube demo showing how guest access can be leveraged to move between environments and extract data.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FLpdckZyBwvs%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DLpdckZyBwvs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FLpdckZyBwvs%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/36e4724978dae3ac242608f6f1330d41/href">https://medium.com/media/36e4724978dae3ac242608f6f1330d41/href</a></iframe><p>This was an eye-opener. A seemingly minor gap in your security posture can expose a significant amount of sensitive information. After watching the demo, I realized we needed to review and disable guest access across our environments immediately.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*81GVxzJgjc5zMJEI" /><figcaption>Photo by <a href="https://unsplash.com/@krivitskiy?utm_source=medium&amp;utm_medium=referral">Alexander Krivitskiy</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Interestingly, the <strong>Power Platform Admin Center</strong> had already flagged this as a recommendation. However, the challenge was that this setting isn’t yet supported in environment groups. With over <strong>1,500 environments</strong>, changing this manually one by one would be unrealistic.</p><p>My first thought was to automate the process using the <strong>Terraform Power Platform provider</strong>. Unfortunately, that functionality wasn’t available yet and the management for personal development environments is done with Environment groups. So, it was time to dig into the APIs and documentation.</p><p>Eventually, I discovered that the setting could be controlled via the restrictGuestUserAccess property at the environment level. At first glance, this looked straightforward—but reality proved otherwise.</p><p>Our deployment process typically starts with internal test environments, followed by updates to personal development environments. During testing, I realized that our management account didn’t have the necessary permissions on those environments. Back to the Admin Center I went, armed with <strong>F12 Developer Tools</strong>. After some investigation, I found that assigning permissions uses the applyAdminRole API call. Unfortunately, this approach didn’t work for our management account.</p><p>Back to the drawing board.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kLstGhC5gHWdIBib" /><figcaption>Photo by <a href="https://unsplash.com/@chappelldigitalmarketing?utm_source=medium&amp;utm_medium=referral">Chase Chappell</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>After reading several blog posts, I discovered that you can add application users using the addAppUser API. That was the breakthrough. I built a short Powershell script to loop through all our personal development environments and apply our management account to those:</p><pre>$personalDevelopmentEnvironments | ForEach-Object -Parallel {<br>  Write-Host &quot;Environment Name: $($_.DisplayName), ID: $($_.name)&quot;<br><br>  $bapHeaders = $using:bapHeaders<br>  $bapBody = $using:bapBody<br>  $count = $using:count<br><br>  $bapApiUrl = &quot;https://api.bap.microsoft.com/providers/Microsoft.BusinessAppPlatform/scopes/admin/environments/$($_.name)/addAppUser?api-version=2020-10-01&quot;<br><br>  try {<br>    Write-Host $bapApiUrl<br>    Invoke-RestMethod -Uri $bapApiUrl -Headers $bapHeaders -Method Post -Body $bapBody<br>    Write-Host &quot;Successful for environment: $($_.DisplayName), ID: $($_.name)&quot;<br>  }<br>  catch {<br>    Write-Host &quot;Failed to fetch environments from BAP API: $($_.Exception.Message)&quot;<br>  }<br>  $count++<br>  Write-Host &quot;Processed environments count: $count&quot;<br>} -ThrottleLimit 5<br>``</pre><p>Once permissions were assigned, it was time to modify the guest access setting itself. This part was more straightforward. I built a Powershell script that loops through all environments, checks the setting, and updates it if necessary:</p><pre>$settingsUrl = &quot;$resource/api/data/v9.2/organizations&quot;<br>try {<br>  $orgs = Invoke-RestMethod -Uri $settingsUrl -Headers $headers -Method Get<br>  if ($orgs.value.restrictGuestUserAccess -ne $true) {<br>    $patchBody = @{<br>      restrictGuestUserAccess = $true<br>    } | ConvertTo-Json<br><br>    $patchUrl = &quot;$resource/api/data/v9.2/organizations($($orgs.value.organizationid))&quot;<br><br>    Invoke-RestMethod -Uri $patchUrl -Headers $headers -Method Patch -Body $patchBody<br><br>    Write-Host &quot;Updated restrictGuestUserAccess to True for environment: $($_.DisplayName)&quot;<br>  }<br>  else {<br>    Write-Host &quot;restrictGuestUserAccess already set to True for environment: $($_.DisplayName)&quot;<br>  }<br>}<br>catch {<br>  Write-Host &quot;Failed to update restrictGuestUserAccess: $($_.Exception.Message)&quot;<br>}</pre><p><strong>✅ Lessons Learned</strong></p><p>You can mange almost all the settings using some of the Power Platform API’s, but they are not well documented.</p><p>I did build Power Automate flow which runs once a day, lists all new environments and assigns management account to them. My next step is to disable the guest access immediately after the creation. Let’s see.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=04df838e1281" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enforcing firewall rules in Power Platform without breaking CoE Starter Kit]]></title>
            <link>https://medium.com/@jerevekka/enforcing-firewall-rules-in-power-platform-without-breaking-coe-starter-kit-0c31ba2c8829?source=rss-e0a688b76a8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/0c31ba2c8829</guid>
            <category><![CDATA[powerplatform]]></category>
            <category><![CDATA[microsoft-power-platform]]></category>
            <dc:creator><![CDATA[Jere Vekka]]></dc:creator>
            <pubDate>Tue, 30 Sep 2025 08:01:06 GMT</pubDate>
            <atom:updated>2025-09-30T08:01:06.623Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the big steps we’ve been taking lately in our Power Platform governance journey is <strong>enforcing firewall rules</strong> on environments. For a large organization like ours, this is a no-brainer for security: we want to make sure only trusted networks can access our environments.</p><p>Sounds simple enough, right? Well, as always, the devil is in the details.</p><h3>Why We Did It</h3><p>Security is a top priority for us. Firewalls help us:</p><ul><li>Reduce the attack surface.</li><li>Keep environments accessible only from corporate networks.</li><li>Meet compliance requirements.</li></ul><p>So, we started enabling firewalls across our environments. Everything looked good — until we noticed something unexpected.</p><h3>The Problem: CoE Starter Kit Stopped Working</h3><p>If you’re using the <strong>Center of Excellence (CoE) Starter Kit</strong>, you know how important it is for visibility and governance. It’s our main tool for understanding what’s happening in the tenant: environments, apps, flows, makers — you name it.</p><p>After enabling firewalls, we suddenly saw that <strong>CoE sync stopped working</strong>. No new data, no updates and a lot of issues with <strong>Admin | Sync*</strong> flows. At first, we thought something was wrong with the CoE setup. But after some digging, we realized the issue: <strong>our firewall rules were blocking the connectors that CoE uses to pull data</strong>.</p><h3>The Fix: Allow the Right Connectors</h3><p>To keep CoE functional while enforcing firewall rules, you need to <strong>allow specific tags</strong>. In our case, the key ones were:</p><ul><li><strong>AzureConnectors</strong> — This is essential for many admin and governance operations.</li><li><strong>PowerPlatformPlex</strong> — This one might also be needed depending on your setup.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/485/1*qbKWthRgH7GWVSeI6xwu2w.png" /><figcaption>Allowed service tags.</figcaption></figure><p>Without these, CoE can’t talk to your environments, and your governance dashboards will go dark.</p><p>You can read more about the IP’s and addresses behing the tags from <a href="https://www.microsoft.com/en-us/download/details.aspx?id=56519">Download Azure IP Ranges and Service Tags — Public Cloud from Official Microsoft Download Center</a></p><h3>What We Did</h3><p>Here’s how we fixed it:</p><ol><li>Went to <strong>Power Platform Admin Center</strong>.</li><li>Opened the environment, Settings and Privacy + Security. Searched the IP address settings and Allowed list of Service Tags.</li><li>Added: AzureConnectors and PowerPlatformPlex (just to be safe)</li><li>Saved the changes and tested the CoE sync — it worked again!</li></ol><h3>Lessons Learned</h3><ul><li>Security and functionality can coexist, but you need to plan for it.</li><li>Always test firewall changes in a <strong>sandbox</strong> before rolling them out.</li><li>Document the required exceptions for governance tools like CoE.</li><li>Production is best place to test if you prefer ScreamOps ;)</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0c31ba2c8829" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Managing large Power Platform tenants: How did we break our automation with Environment Groups]]></title>
            <link>https://medium.com/@jerevekka/managing-large-power-platform-tenants-how-did-we-break-our-automation-with-environment-groups-a1f81fc6dae1?source=rss-e0a688b76a8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1f81fc6dae1</guid>
            <category><![CDATA[microsoft-power-platform]]></category>
            <category><![CDATA[powerplatform]]></category>
            <dc:creator><![CDATA[Jere Vekka]]></dc:creator>
            <pubDate>Mon, 29 Sep 2025 06:47:27 GMT</pubDate>
            <atom:updated>2025-09-29T06:48:00.834Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’re working with <strong>Power Platform</strong> in a large organization, you already know the challenge: how do you keep things secure, compliant, and manageable when you have <strong>hundreds or even thousands of environments</strong>?</p><p>I’ve been living this reality for the past 18+ months as a <strong>Senior Specialist</strong>, where we manage a tenant with <strong>over 1,000 environments</strong>. Our goal has always been clear: <strong>make governance easy, automated, and reliable</strong>.</p><p>One of the key tools we use for this is <strong>Terraform</strong>. With the Power Platform Terraform provider, we’ve been able to:</p><ul><li>Automate environment creation and configuration.</li><li>Apply consistent governance policies.</li><li>Keep everything version-controlled and auditable.</li></ul><p>This approach has worked well — until Microsoft introduced <strong>Environment Groups</strong> (and we did test them).</p><h3>Environment Groups: A great way to manage some settings with some surprises</h3><p>Microsoft recently rolled out Environment Groups, which promise to make governance easier by letting you group environments and apply rules at scale. On paper, this is exactly what large organizations need.</p><p>Naturally, we started testing it. And here’s what we found:</p><h3>1. Managed Environment settings get locked</h3><p>As soon as you enable an environment group for an environment, <strong>all Managed Environment settings become locked</strong>, even if the group has <strong>no rules defined</strong>. This is not what the documentation suggests — it says settings should only be enforced when rules exist. So, this was a surprise. This effects only the Managed Environments settins like <strong>sharing settings</strong>, <strong>Solution checker enforcement</strong> and <strong>Maker welcome content</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/549/1*vtFxKaabV-EaCi8mNQDfZg.png" /><figcaption>Managed Environment settins locked out.</figcaption></figure><h3>2. Terraform Management Breaks</h3><p>The bigger issue for us: once an environment is part of an environment group, <strong>Terraform can no longer manage it</strong>. This is a major problem if you rely on Infrastructure as Code for governance. We’ve reported this bug to the team behind the Power Platform Terraform provider, but for now, it’s a limitation you need to be aware of.</p><p>Currently it seems that, the management with Terraform is not possible even if the environment is removed from the Environment group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*QGXgIkWXiv26-y0tTnm6nQ.png" /><figcaption>Power Platform provider breaks after environment groups is enabled.</figcaption></figure><h3>3. Other settings can be still changed… but not really</h3><p>Here’s another interesting behavior: when environment group rules are published, <strong>settings outside of Managed Environment options are not locked</strong>. You can still go into the admin center and change them manually. However, those changes <strong>don’t stick</strong> — they’re automatically reverted to comply with the environment group rules.</p><p>This can be confusing for admins because:</p><ul><li>It looks like you can make changes.</li><li>There’s no immediate warning that the change will be undone.</li><li>The reversal happens when you try to save settings.</li></ul><p>So, if you see settings “mysteriously” reverting, this is why.</p><h3>What does this mean for you?</h3><p>If you’re managing Power Platform at scale:</p><ul><li><strong>Test Environment Groups in a sandbox first</strong> before rolling them out widely.</li><li>Be aware that enabling them may disrupt your automation workflows.</li><li>Communicate clearly to your admin teams that some settings will auto-revert.</li></ul><p><strong>GL &amp; HF. Try not to break your environments.</strong></p><p>ps. If you have found a way to make Power Platform provider work again, please let me know :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1f81fc6dae1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>