<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Governance on RLGeeX</title><link>https://www.rlgeex.com/tags/governance/</link><description>Recent content in Governance on RLGeeX</description><generator>Hugo</generator><language>en-us</language><copyright>RLGeeX © 2025 - Real-Life Geeks providing expert IT consulting</copyright><lastBuildDate>Tue, 10 Nov 2026 09:00:00 -0500</lastBuildDate><atom:link href="https://www.rlgeex.com/tags/governance/index.xml" rel="self" type="application/rss+xml"/><item><title>Organization Policies at Scale: Attach High, Pick Managed Constraints, Roll Out in Dry Run</title><link>https://www.rlgeex.com/news/organization-policies-at-scale-attach-high-pick-managed-constraints-roll-out-in-/</link><pubDate>Tue, 10 Nov 2026 09:00:00 -0500</pubDate><guid>https://www.rlgeex.com/news/organization-policies-at-scale-attach-high-pick-managed-constraints-roll-out-in-/</guid><description>&lt;p>This post is for cloud engineers building a GCP foundation with Terraform who want Organization Policy to keep working once the hierarchy grows past a few projects. My argument is that org policy at scale comes down to three decisions. Attach constraints as high in the hierarchy as you can. Handle exceptions with conditions, not scattered overrides. Once other teams own workloads, never enforce a new constraint until it has run in dry-run mode. By the end you should know where each policy belongs, which kind of constraint to reach for, and how to promote one from observed to enforced.&lt;/p></description></item></channel></rss>