There are two things about controlling #Azure costs that I've learned over time:
1). Do _not_ restrict or buffer architects and devs from cost data. Otherwise, they will be profilgate.
2). Give each team a test subscription with a strict, never-allowed-to-exceed cost limit using Azure Cost Management. That way, people learn NOT to be profligate.
Alex Neihaus /
npub1ut…2h5at
2024-03-18 14:59:50
Author Public Key
npub1utrn3duez00n4wc6uhrh8er82rqc6vzzmhy76h6dtrn8wlg2exjqd2h5atPublished at
2024-03-18 14:59:50Event JSON
{
"id": "f861b9a5e5f19d4bc29a5ef691709b67dad05af86e5a6f31d1aa3d52e93026b5",
"pubkey": "e2c738b79913df3abb1ae5c773e46750c18d3042ddc9ed5f4d58e6777d0ac9a4",
"created_at": 1710770390,
"kind": 1,
"tags": [
[
"t",
"azure"
],
[
"proxy",
"https://air11.social/users/alex/statuses/112117048296983930",
"activitypub"
]
],
"content": "There are two things about controlling #Azure costs that I've learned over time:\n\n1). Do _not_ restrict or buffer architects and devs from cost data. Otherwise, they will be profilgate.\n\n2). Give each team a test subscription with a strict, never-allowed-to-exceed cost limit using Azure Cost Management. That way, people learn NOT to be profligate.",
"sig": "aa8347c9b117e5e43b7c4d1afdc305b63f926c0d8b8408381262b107e52309a2a6aa177a040afdbff1550202d72a05898f47e229fe4cf60f2435ac4fe8ae6766"
}