Hello eveyone, I am very happy to share exciting news with all of you.
Few days ago, i have receieved an email confirming acceptance of my both Azure sessions for the Global Azure 2021 event. I am truely trilled to present on April 16th and 17th following two sesions for eveyone live:
I am looking forward for your participiation, and tune in to learn about latest developments in Microsoft Azure.
In my first session i will share the following new session with you.
Abstract of the presentation as is:
Infrastructure as a Code (IaC) is important strategy to manage your digital estate in any cloud environment. Simplifying management of your infrastructure while re-using code is even better. In Microsoft Azure, we have ARM (Azure Resource Manager) templates that could declaratively define your cloud project infrastructure.
However, it is not easy to author ARM JSON templates and maintain them when your project grows and requires changes. In this demo heavy session, we will introduce the Azure Bicep language and demonstrate how it simplifies authoring ARM templates for your Azure infrastructure. We will author a manageable, readable, and modularized Azure infrastructure code, while using familiar tools.
Please let me know, what topics are you interested in?
It is usually hard to start a new initiative within a company due to a myriad of reasons. 🤔 Thus, this post will focus on how to follow some descriptive steps in starting a new Cloud Journey whereever you are in your life 🙂
Let’s check a simple approach 💡 below that could guide us on cloud ☁️ (AWS, Azure, GCP, Oracle Cloud) adoption journey 🗺
1️⃣ Step: Check on Team Alignment with cloud fundamentals ✔️ Every team member should have a basic understand of how specific cloud works ✔️ Portfolio of candidate workloads should be available to all team members to be used during strategic, release planning and completion of technical tasks ✔️ The technical strategy should include clarity on which levels of the hosting hierarchy will be used and what those terms mean in our business ✔️ A naming and tagging standard should be established, maintained, and enforced to guide implementation and resource organization ✔️ The hosting hierarchy should be reflected in a resource organization design (account or subscription design) ✔️ Align cloud capabilities, teams, and RACI structure to the fundamental concepts above
As an addition, what would you add into first checklist ? 🤔