Azure Deployments AMA
We are very excited to announce an Azure Deployments AMA! Join the Azure Deployments team to discuss all things Infrastructure as Code (IaC) in Azure. The panelists own all of the most popular declarative IaC tooling for Azure including ARM Templates, Bicep and Terraform. They want to hear what is on your mind so bring your IaC questions and hear from the experts. An AMA is a live text-based online event similar to a “YamJam” on Yammer or an “Ask Me Anything” on Reddit. This AMA gives you the opportunity to connect with Microsoft product experts who will be on hand to answer your questions and listen to feedback. Feel free to post your questions about Azure Deployments anytime in the comments below beforehand, if it fits your schedule or time zone better, though questions will not be answered until the live hour.Tech Accelerator: Mastering Azure and AI adoption
Join us to learn about the essential guidance, resources, products and tooling you need to accelerate your next Azure and AI project or enhance your existing Azure deployments. Get in-depth technical guidance from Microsoft experts to enhance the reliability, security and ongoing performance of your Azure workloads. Learn more about AMD products and solutions to accelerate cloud adoption. Now on demand! Best practices for secure and reliable Azure projects Govern, manage and secure your AI deployments How to run a successful Azure migration project Advance cloud infrastructure: Essentials with AMD on Azure Essentials to build and modernize AI applications on Azure Proactively design, deploy & monitor resilient Azure workloads Cloud platform security in an evolving threat landscapeDigital event: The Future of VMware Is in Azure
Take a technical deep dive into solutions for VMware workloads in a rapidly evolving VMware landscape. Join us on July 16 to build your technical expertise with sessions just for VMware administrators. Securing your future: Migrate applications and data to Azure VMware Solution. Understand how to migrate your apps and data securely while implementing the Zero-Trust security model and designing proper role-based access control within Azure VMware Solution. Building end-to-end networking with Azure VMware Solution. Get to know Azure VMware Solution networking architecture and see a demo of key connectivity patterns from your software-defined data center in Azure VMware Solution to your on-premises environment. Implementing a robust business continuity and disaster recovery plan with Azure VMware Solution. Take a deep dive into common use case scenarios and explore best practices for implementing your business continuity and disaster recovery strategy using Azure VMware Solution. Unlocking Azure cloud services with Azure VMware solution. See demos of how to use services on the Azure platform to expand the capabilities of your applications on Azure VMware Solution—without changes to your existing app architecture. Hybrid cloud options for VMware workloads. Explore hybrid cloud solutions as a complement to the public cloud. This session will show you how to combine Azure Arc, Azure Stack HCI, and Arc-enabled vSphere to create a seamless, adaptive cloud experience. Register now > The Future of VMware Is in Azure Tuesday, July 16, 2024 9:00 AM–11:00 AM Pacific Time (UTC-7)Preparing for the unexpected: Azure & Power Platform (Incident Readiness) - Session 1
Join our upcoming webcast to hear about best practices from our engineering experts – including how to prevent impact from incidents by building resilient applications, and how to protect your cloud environments. You will also have access to live Q&A in the side panel, to get your incident readiness questions answered by our subject matter experts. Two session options, same content presented, both with Live Q&A available: Since building reliable and secure applications on Azure is a shared responsibility, join us to learn from live demonstrations that will empower you to implement our incident readiness recommendations. We will help you understand how to prevent the impact of incidents, protect your environment, and remain informed throughout incident lifecycles. Join us to get familiar with: Our Power Platform team’s journey to identify, assess, and improve the resilience of their own Azure services – which power critical customer-facing workloads – using Availability Zones How to assess whether the resources that support your mission-critical services are sufficiently zone-resilient, using Azure Advisor recommendations and workbooks Balancing competing priorities as you invest in resilience and security, with an eye on cost optimization using best practices from the Azure Well-Architected Framework Retrofitting your existing Virtual Machines and Azure Disks, for zone resiliency and redundancy, respectively – to minimize and avoid impact from common incident types Understand and control who can access your resources – including using Microsoft-managed Conditional Access Policies, and recommended actions to raise your security baseline This approach will bring our incident readiness guidance to life, and get you connected with subject matter experts so that you can ask any clarifications or follow up questions during the session. Please join us – register for your preferred session timeslot, using the registration links. Register for session option #1 Wednesday 24 January @ 8 - 9 AM PST (Wednesday 24 January @ 16:00 UTC). Register here for session option #2 Wednesday @ 8 - 9 PM PST (Thursday 25 January @ 04:00 UTC). Incident Readiness Resources Prepare for the unexpected. Learn how you can mitigate impact, protect your investment, and stay informed. Microsoft categorizes cloud incidents into three types: service incidents, privacy incidents, and security incidents. A service incident is an event or a series of events that can cause an interruption or degraded experience for customers using one or more of Microsoft's services. These incidents are effectively unplanned downtime – including outages impacting availability, performance degradation impacting users, and problems interfering with service administration/management. Privacy incidents relate to potential unauthorized use or disclosure of customer data. Finally, security incidents in Microsoft's online services refer to confirmed breaches of security resulting in accidental or unlawful destruction, loss, alteration, unauthorized disclosure, or access to customer or personal data while being processed by Microsoft. Please review the cloud specific incident readiness sections that covers steps you should take to prepare and protect your environment and what actions you should take or be aware of during an incident. Read More: Azure Incident Readiness Microsoft 365, Dynamics 365 Power & Power Platform Incident ReadinessModernize and Migrate with Hybrid Cloud Flexibility
Gain skills and knowledge to confidently navigate your cloud journey directly from Azure customers and experts at this free digital event. Register today, for this free digital event on April 13th, 2022 https://aka.ms/AzureModernizationDigitalEventPasso a Passo para Criar um Filtro de Tag no FinOps Hub
Recentemente, publiquei um blog sobre implementação e gerenciamento de custos do Azure usando FinOps Hub no formato FOCUS. Confira aqui. Agora, vou explicar como criar um filtro de Tag no FinOps Hub para otimizar a gestão de custos. 1. Acesse o Dashboard CostSummary do FinOps Hub Primeiro, abra o seu dashboard CostSummary do FinOps Hub. Esta versão que estamos trabalhando seria a V0.4. Em seguida, clique na aba de Resources. Você vai notar na tabela que existe uma coluna de Tag, porém ela não está formatada e não possui um filtro. O objetivo é corrigir a coluna e adicionar um filtro de tag para centro de custo. As Tags são referentes ao meu ambiente. De acordo com a figura abaixo, selecione a opção para transformar dados e adicionaremos o filtro de tag. 2. Navegue até a Seção de Filtragem No painel principal, localize e clique em CostDetails. Em seguida, encontre a coluna x_TagsDictionary, clique no item ao lado do nome e selecione a Tag centro_de_custo. No meu exemplo, também adicionei a Tag Environment. Antes de clicar em OK, desmarque a opção "Use original column name as prefix." E em seguida clique em OK 3. Selecione "Criar Novo Filtro" Ao clicar em OK, serão adicionadas mais duas colunas, centro_de_custo e Environment, conforme ilustrado no exemplo abaixo. Em seguida clique em Close & Apply 4. Criação do Fitro de Tag Na View de Resources, copie e cole o filtro de subscription com Ctrl+C e Ctrl+V e arraste-o para perto da view de Total Savings. 5. Alterar o Filtro Subscription para Filtro de Tag Selecione o filtro Subscription e, em Data, localize a tag centro_de_custo. Arraste o item centro_de_custo para field e depois exclua o Field Subscription. 6. Nova View para o Filtro Centro de Custo A visualização será parecida com o exemplo a seguir 7. Alterar a Tabela para fitrar por Tag Centro De Custo Precisamos agora modificar a tabela para aplicar o filtro ao centro de custo. Selecione a tabela e encontre no campo Data a tag centro_de_custo. Arraste o item centro_de_custo nas Colunas, como mostrado abaixo, e remova Tags da coluna. Com essas etapas concluídas, você deve ter uma nova visualização que reflete o filtro aplicado ao centro de custo. Essa configuração permitirá uma análise mais detalhada e específica, facilitando a identificação de gastos associados a cada centro de custo. Finalmente, salve as alterações feitas e atualize o dashboard para garantir que todas as modificações foram aplicadas corretamente. Agora, ao utilizar o filtro de centro de custo, você poderá visualizar apenas os dados relevantes conforme sua necessidade, tornando a análise financeira mais eficiente e direcionada.Preparing for the unexpected: Azure & Power Platform (Incident Readiness) - Session 2
Join our upcoming webcast to hear about best practices from our engineering experts – including how to prevent impact from incidents by building resilient applications, and how to protect your cloud environments. You will also have access to live Q&A in the side panel, to get your incident readiness questions answered by our subject matter experts. Two session options, same content presented, both with Live Q&A available: Since building reliable and secure applications on Azure is a shared responsibility, join us to learn from live demonstrations that will empower you to implement our incident readiness recommendations. We will help you understand how to prevent the impact of incidents, protect your environment, and remain informed throughout incident lifecycles. Join us to get familiar with: Our Power Platform team’s journey to identify, assess, and improve the resilience of their own Azure services – which power critical customer-facing workloads – using Availability Zones How to assess whether the resources that support your mission-critical services are sufficiently zone-resilient, using Azure Advisor recommendations and workbooks Balancing competing priorities as you invest in resilience and security, with an eye on cost optimization using best practices from the Azure Well-Architected Framework Retrofitting your existing Virtual Machines and Azure Disks, for zone resiliency and redundancy, respectively – to minimize and avoid impact from common incident types Understand and control who can access your resources – including using Microsoft-managed Conditional Access Policies, and recommended actions to raise your security baseline This approach will bring our incident readiness guidance to life, and get you connected with subject matter experts so that you can ask any clarifications or follow up questions during the session. Please join us – register for your preferred session timeslot, using the registration links. Register for session option #1 Wednesday 24 January @ 8 - 9 AM PST (Wednesday 24 January @ 16:00 UTC). Register here for session option #2 Wednesday @ 8 - 9 PM PST (Thursday 25 January @ 04:00 UTC). Incident Readiness Resources Prepare for the unexpected. Learn how you can mitigate impact, protect your investment, and stay informed. Microsoft categorizes cloud incidents into three types: service incidents, privacy incidents, and security incidents. A service incident is an event or a series of events that can cause an interruption or degraded experience for customers using one or more of Microsoft's services. These incidents are effectively unplanned downtime – including outages impacting availability, performance degradation impacting users, and problems interfering with service administration/management. Privacy incidents relate to potential unauthorized use or disclosure of customer data. Finally, security incidents in Microsoft's online services refer to confirmed breaches of security resulting in accidental or unlawful destruction, loss, alteration, unauthorized disclosure, or access to customer or personal data while being processed by Microsoft. Please review the cloud specific incident readiness sections that covers steps you should take to prepare and protect your environment and what actions you should take or be aware of during an incident. Read More: Azure Incident Readiness Microsoft 365, Dynamics 365 Power & Power Platform Incident Readiness
Azure SDK for Go Fundamentals | Azure SDK Community Standup
Welcome to the Azure SDK Team channel, where we explore the latest updates and features of Azure development tools and services. In this episode, we will learn about the benefits, key features, and functionality of Azure SDK for Go. Join us as we demonstrate how to effectively use the Azure client libraries for Go, empowering you to harness the full potential of Azure services in your projects. Don't forget to like, share, and subscribe to stay updated with the latest Azure development updates and features. https://aka.ms/azsdk/releases https://aka.ms/azsdk/blog https://aka.ms/azsdk/github https://twitter.com/AzureSDK Community Links: https://www.theurlist.com/azuresdk Featuring: Hector Norzagaray @HectorOnAzure, Richard Park @ParkPlusPlus, Sandeep Sen Sandeep_K_Sen #AzureSDK #AzureDev #MicrosoftAsk the product experts live: SAP on Azure and Azure VMware Solution
Organizations are extending their mission-critical workloads to the cloud to unlock key benefits such as uncovering critical business insights from their SAP data or bringing cloud native services to existing VMware investments. Join the product experts live from the SAP on Azure and Azure VMware Solution teams to have all your questions answered in real time and to learn about modernizing your mission-critical workloads with Azure. Tune in live on Microsoft Learn TV on Tuesday, August 17th at 11am pacific time, and be sure to sign in ahead of time with your Microsoft account to add your questions during the live event. Learn more about SAP on Azure and Azure VMware Solution: Accelerate your digital transformation with key insights from Erin Chapple, Julia White (SAP), and Mark Lohmeyer (VMware): Accelerate digital transformation with SAP and VMware on Azure Improve your cloud infrastructure skills with advanced guidance from SAP on Azure and Azure VMware Solution product experts: Expert series on-demand videos Start the discussion today! What questions do you have? Add them to the 'Comments' box below.
Zonas de Disponibilidade no Azure: Entendendo a Diferença entre Zonas Lógicas e Físicas
O que é o mapeamento de zonas do Azure (Zona Lógica vs Zona Física) No Azure, as Zonas de Disponibilidade (AZs) são agrupamentos de datacenters fisicamente separados dentros de uma mesma região. Cada zona possui infraestrutura independente - energia, refrigeração e rede - garantindo alta disponibilidade e resiliência. Porém, há uma distinção entre: Tipo de Zona Definição Zona Lógica Identificador exibido no portal do Azure (AZ1, AZ2, AZ3). Zona Física Grupo real de datacenters. O mapeamento entre lógica e física varia por assinatura O mapeamento entre zonas lógicas e físicas não é fixo. Isso significa que: AZ1 na assinatura A pode ser fisicamente igual à AZ3 na assinatura B. Sem verificação, você pode estar executando produção e DR na mesma infraestrutura física, anulando os benefícios da separação. Esse comportamento é intencional e inspirado no modelo da AWS, que também não garante consistência entre zonas lógicas em diferentes contas. Qual o objetivo desse design? A motivação por trás desse mapeamento dinâmico é: Distribuir a carga de consumo de forma mais eficiente entre os datacenters. Evitar hotspots e garantir resiliência operacional. Permitir flexibilidade de alocação conforme a capacidade física disponível. Esse modelo ajuda a balancear o uso da infraestrutura global, sem expor diretamente a topologia física aos clientes — o que também reforça a segurança e abstração da plataforma. Essa distinção é essencial: a zona lógica AZ1 em uma assinatura pode, na prática, ser a mesma zona física que a AZ3 em outra. Sem uma verificação adequada, o cliente pode acabar executando cargas de produção e de DR (Disaster Recovery) na mesma infraestrutura física, o que anula os benefícios esperados da separação entre zonas. Exemplo prático de risco Vamos considerar o seguinte cenário de um cliente: Produção: AZ1 e AZ2 em uma assinatura A DR: AZ3 em outra assinatura B, na mesma região O cliente acredita estar distribuindo suas cargas entre três zonas distintas. No entanto, ao verificar o mapeamento real, encontra a seguinte saída: [ { "logicalZone": "1", "physicalZone": "brazilsouth-az3" }, { "logicalZone": "2", "physicalZone": "brazilsouth-az1" }, { "logicalZone": "3", "physicalZone": "brazilsouth-az2" } ] Neste exemplo, a AZ3 lógica está mapeada para a AZ2 física, que já está sendo usada na produção. Ou seja, não há separação física real. Como verificar o mapeamento de zonas? Para evitar esse problema, é essencial verificar o mapeamento entre zonas lógicas e físicas em cada assinatura. Use o seguinte comando via Azure CLI: az rest --method get \ --uri "/subscriptions/<subscription-id>/locations?api-version=2022-12-01" \ --query "value[?name=='<region-name>'].{displayName: displayName,name: name,availabilityZoneMappings: availabilityZoneMappings }" \ -o json Substitua <subscription-id> e <region-name> (ex: brazilsouth) conforme necessário. Veja abaixo um exemplo de saída obtida no meu ambiente de laboratório, onde tenho duas assinaturas. Vou executar o mapeamento de zonas entre elas para a região Brazil South. Na primeira subscription 1 temos o seguinte mapeamento. Zona lógica: 1 – Zona Física: brazilsouth-az1 Zona lógica: 2 – Zona Física: brazilsouth-az2 Zona lógica: 3 – Zona Física: brazilsouth-az3 Na segunda subscription 2 temos o seguinte mapeamento. Zona lógica: 1 – Zona Física: brazilsouth-az3 Zona lógica: 2 – Zona Física: brazilsouth-az1 Zona lógica: 3 – Zona Física: brazilsouth-az2 Resumindo: Se minha estratégia de DR envolve o uso das zonas lógicas 1 e 2 na subscription 1, pois elas estão mapeadas fisicamente para as zonas AZ1 e AZ2, então, na subscription 2 destinada ao DR, devo utilizar a zona lógica 1 — já que, nessa assinatura, ela está mapeada fisicamente para a AZ3. Boas práticas Sempre verifique o mapeamento entre zonas lógicas e físicas antes de definir sua estratégia de DR. Evite assumir que AZ1, AZ2 e AZ3 representam zonas físicas distintas entre diferentes assinaturas. Considere utilizar regiões diferentes para DR quando a separação física for um requisito crítico. Documente e compartilhe o mapeamento com sua equipe de arquitetura e operações para garantir alinhamento e evitar riscos. Referência oficial Para mais detalhes, consulte a documentação oficial da Microsoft: https://learn.microsoft.com/en-us/azure/availability-zones/az-overview Comparing AWS and Azure regions and zones - Azure Architecture Center | Microsoft Learn
