<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Naming Convention on Niels Ophey</title><link>https://www.ophey.net/en/tags/naming-convention/</link><description>Recent content in Naming Convention on Niels Ophey</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 18 Jul 2022 13:07:02 +0200</lastBuildDate><atom:link href="https://www.ophey.net/en/tags/naming-convention/index.xml" rel="self" type="application/rss+xml"/><item><title>CAF Naming Convention</title><link>https://www.ophey.net/en/blog/caf-namingconvention/</link><pubDate>Mon, 18 Jul 2022 13:07:02 +0200</pubDate><guid>https://www.ophey.net/en/blog/caf-namingconvention/</guid><description>&lt;h2 id="naming-convention">Naming Convention&lt;/h2>
&lt;p>There is always a big discussion about how to implement a naming convention for Azure resources to be deployed. Often this &lt;a href="https://docs.microsoft.com/azure/cloud-adoption-framework/ready/azure-best-practices/resource-naming">article&lt;/a> from the Microsoft Cloud Adoption Framework for Azure is used as a starting point for an organization&amp;rsquo;s own implementation.&lt;/p></description></item></channel></rss>