<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Power Platform on Tomas Pivny</title>
		<link>https://www.tompivny.com/tags/power-platform/</link>
		<description>Recent content in Power Platform on Tomas Pivny</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Sun, 01 Nov 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://www.tompivny.com/tags/power-platform/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>ALM of managed identities for Dataverse plug-ins</title>
				<link>https://www.tompivny.com/posts/alm-of-managed-identities-for-dataverse-plug-ins/</link>
				<pubDate>Sun, 01 Nov 2026 00:00:00 +0000</pubDate>
				<guid>https://www.tompivny.com/posts/alm-of-managed-identities-for-dataverse-plug-ins/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;https://learn.microsoft.com/en-us/power-platform/admin/managed-identity-overview&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;Managed identities in Dataverse plug-ins&lt;/a&gt; have been around for a couple of years now. They provide a secretless way of authentication from the plug-in sandbox to other Entra-aware resources and applications (most commonly, but not exclusively, used to authenticate against various Azure resources). So far, I have been avoiding this authN method as I did not hear the most positive feedback from the community regarding the whole setup and, most importantly, handling the whole lifecycle including automated deployment. Well, I finally found a use case for plug-in managed identities, so for me that means the application lifecycle management (ALM) needs to be handled first.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
