From 6461c86ac6a8a1bc3436077bcf6d9054dc1b8e26 Mon Sep 17 00:00:00 2001
From: bhecknr <114170582+bhecknr@users.noreply.github.com>
Date: Tue, 6 Jun 2023 14:19:30 -0600
Subject: [PATCH] Update usage-dictionary.mdx

Added "Azure naming conventions" to Usage dictionary.
---
 .../docs/style-guide/word-choice/usage-dictionary.mdx      | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/src/content/docs/style-guide/word-choice/usage-dictionary.mdx b/src/content/docs/style-guide/word-choice/usage-dictionary.mdx
index 181936fbed4..9acc216faf2 100644
--- a/src/content/docs/style-guide/word-choice/usage-dictionary.mdx
+++ b/src/content/docs/style-guide/word-choice/usage-dictionary.mdx
@@ -80,6 +80,13 @@ For consistency across New Relic content, here are our general word usage guidel
     The "machine name" that the collector uses to uniquely identify an app is its `app name`. The server-side configuration setting that changes the visible "name" of an app without changing its unique identifier is its `app alias`.
   </Collapser>
 
+  <Collapser
+    id="Azure naming conventions"
+    title="Azure naming conventions"
+  >
+    Use Microsoft Azure cloud computing platform naming conventions as prescribed by Microsoft; it’s what customers understand and recognize. For example, Azure Native New Relic Service.
+  </Collapser>
+  
   <Collapser
     id="backend"
     title="backend"