Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://awscommunity.social/users/Quinnypig/statuses/111570044004583798">Corey Quinn (quinnypig@awscommunity.social)'s status on Wednesday, 13-Dec-2023 09:06:16 JST</a><a href="https://awscommunity.social/@Quinnypig" title="quinnypig@awscommunity.social"><img src="https://gnusocial.jp/avatar/78666-48-20240327014540.webp" width="48" height="48" alt="Corey Quinn" style="position: absolute; left: 0; top: 0;">Corey Quinn</a><div><a href="https://awscommunity.social/@Quinnypig/111570031870903881" rel="in-reply-to">in reply to</a></div></section><article><p>Azure cautions include:</p><p>* it catches fire a lot due to neighborhood kids sneaking into the data centers through all of the doors that were left propped open</p><p>* lock-in because they dare to make things that work well together</p><p>* becoming a partner is like getting ordained online</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/2445786#notice-4836946">In conversation</a><time datetime="2023-12-13T09:06:16+09:00" title="Wednesday, 13-Dec-2023 09:06:16 JST">about a year ago</time> <span>from <span><a href="https://awscommunity.social/@Quinnypig/111570044004583798" rel="external" title="Sent from awscommunity.social via ActivityPub">awscommunity.social</a></span></span><a href="https://awscommunity.social/@Quinnypig/111570044004583798">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/1956787">text, letter with text Cautions • Persistent resilience and security issues: Despite Microsoft's ongoing efforts, the Azure outage in Singapore in January of 2023 illustrated that inconsistent operational practices and failover architectures remain an issue in some regions. Further, serious security vulnerabilities in Azure have been made public by researchers over the past two years. Microsoft is currently in the process of addressing its security posture and working to foster a more security-first culture. • Cross-service dependencies and technology lock-in: Many Gartner clients report frustration with how Azure services are purpose-built to "work best" with other Azure services, such that controlling the spread of Azure in an account is difficult. Often the cost implications of using a new Azure service just to meet the needs of another Azure service are not clear to customers, who then see their Azure bill spike in unforeseen ways. • Uneven partner and unified support quality: Micr</a></label><br><a href="https://cdn.masto.host/awscommunitysocial/media_attachments/files/111/570/034/544/393/467/original/ab0a9d6804a73f61.png" rel="external">https://cdn.masto.host/awscommunitysocial/media_attachments/files/111/570/034/544/393/467/original/ab0a9d6804a73f61.png</a></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Corey Quinn (quinnypig@awscommunity.social)'s status on Wednesday, 13-Dec-2023 09:06:16 JST Corey Quinn
in reply to
Azure cautions include:
* it catches fire a lot due to neighborhood kids sneaking into the data centers through all of the doors that were left propped open
* lock-in because they dare to make things that work well together
* becoming a partner is like getting ordained online
In conversationabout a year ago from awscommunity.socialpermalink
Attachments
1. text, letter with text Cautions • Persistent resilience and security issues: Despite Microsoft's ongoing efforts, the Azure outage in Singapore in January of 2023 illustrated that inconsistent operational practices and failover architectures remain an issue in some regions. Further, serious security vulnerabilities in Azure have been made public by researchers over the past two years. Microsoft is currently in the process of addressing its security posture and working to foster a more security-first culture. • Cross-service dependencies and technology lock-in: Many Gartner clients report frustration with how Azure services are purpose-built to "work best" with other Azure services, such that controlling the spread of Azure in an account is difficult. Often the cost implications of using a new Azure service just to meet the needs of another Azure service are not clear to customers, who then see their Azure bill spike in unforeseen ways. • Uneven partner and unified support quality: Micr
  https://cdn.masto.host/awscommunitysocial/media_attachments/files/111/570/034/544/393/467/original/ab0a9d6804a73f61.png

Public

Embed Notice

HTML Code

Corresponding Notice