SOLVED

Azure subscription and pricing model

%3CLINGO-SUB%20id%3D%22lingo-sub-1484001%22%20slang%3D%22en-US%22%3EAzure%20subscription%20and%20pricing%20model%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1484001%22%20slang%3D%22en-US%22%3E%3CP%3ECould%20someone%20clarify%20the%20naming%20convention%20for%20Azure%20subscription%20and%20how%20that%20will%20reflect%20on%20billing%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1484046%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20subscription%20and%20pricing%20model%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1484046%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F707994%22%20target%3D%22_blank%22%3E%40michaelbyrd%3C%2FA%3E%26nbsp%3BSince%20there%20are%20so%20many%20resource%20times%20in%20the%20Azure%20resource%20environment%20I%20would%20recommend%20checking%20out%20the%20naming%20and%20tagging%20guidance%20doc%20here%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fcloud-adoption-framework%2Fready%2Fazure-best-practices%2Fnaming-and-tagging%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fcloud-adoption-framework%2Fready%2Fazure-best-practices%2Fnaming-and-tagging%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1484054%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20subscription%20and%20pricing%20model%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1484054%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F25394%22%20target%3D%22_blank%22%3E%40Jef%20Kazimer%3C%2FA%3E%26nbsp%3BThis%20is%20perfect%20thank%20you%20jef%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Could someone clarify the naming convention for Azure subscription and how that will reflect on billing? 

2 Replies
Highlighted

@michaelbyrd Since there are so many resource times in the Azure resource environment I would recommend checking out the naming and tagging guidance doc here https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/naming-an...

Highlighted
Solution

@Jef Kazimer This is perfect thank you jef