We started the #CloudMarathoner community and cloud learning journey approximately 3+ years ago with few posts and followers. My main intention in starting this hashtag is to help everyone learn the #cloud #fundamentals & #architecture while sharing training resources that could help you in your awesome #cloud journey.
We ARE GROWING every month
Thank you for your continued feedback and support! Our #CloudMarathoner community is over 1600+ members strong and we are growing it every month. This community of contributors and members like Hugo Barona, Jackson Feldon, new MVP – Martin Dimovski, John Lokerse and many other leaders are able to reach and inspire many more people every day and week.
If you have been implementing your customers with the management of enterprise subscriptions and policies, then it is a pretty common need to automate the provisioning of those subscriptions in a controlled and secure manner.
The good news is that you don’t have to reinvent the wheel and do everything from scratch. The Microsoft team that is behind the Azure Landing Zones implementation has a good reference that could tremendously help you.
Microsoft Global Customer Success team
Have you ever checked the subscription vending IaC Modules from the Microsoft Global Customer Success team (the same team behind Azure Landing Zones)?
Subscription Vending IaC Modules
Well, if not then Subscription Vending IaC Modules are available for you in two popular infrastructure-as-code (IaC) tools: Bicep and Terraform. AND designed to help you implement the best practices for subscription provisioning.
Why use these modules?
Using these modules, you can quickly and easily provision new Azure subscriptions that are pre-configured to meet your organization’s specific needs. The modules include parameters/variables for Role-Based Access Control, Networking, Tags, and more.
In this workshop, you will build a complete application including a website with authentication and 3 microservices, deploy it to Azure using a CI/CD pipeline, monitor and tune the scaling of our services, and use log tracing to debug issues.
This workshop approach is one of many ways to get started with Node.js Microservices in Azure. But, I am interested to hear from you.
What is your preferred way to implement microservices in Azure ⁉ 🤔 Please, share your feedback 💬 in the comments or in the following LinkedIn post.
I hope you will enjoy this reference architecture and the @GitHub code repo. More importantly, you got a chance to learn something new. Hopefully, you’ll be able to take this knowledge back to your projects and improve your solutions.
Let’s focus on answering the main question of this post. And some of you may suspect that we will allude to Azure Arc, right?
Microsoft Azure Arc
Yes, with the Microsoft Azure Arc, you can manage servers running on-premises, at the edge, and in multi-cloud environments. And with the latest updates, now, you also get SSH access to your Linux and Windows Servers running anywhere using Azure Arc-enabled servers.
Direct Network Connectivity
Even though direct network connectivity (like SSH connection into the server) can be a challenge in hybrid and multi-cloud environments, Azure Arc-enabled servers enable this unique capability for you.
What are the Helpful References?
Well, let me mention the following important three references that will get you going in your Azure Arc journey, ok?
I hope this provides you with a good overview and resources of how you can manage and SSH access your Linux and Windows Servers anywhere using Azure Arc. And if you feel like you got a question, please, feel free to leave a comment on my LinkedIn post.
This exam assesses the following DevOps skills: ✔ Configure processes and communications ✔ Design and implement source control ✔ Design and implement build and release pipelines ✔ Develop a security and compliance plan ✔ Implement an instrumentation strategy
Your Support is Appreciated!
Thank you 🙏 T-Rex Solutions, LLC for a strong and relentless learning culture and for supporting my Microsoft #MVP journey 👏
Anyone who manages Azure resources knows that consistent naming is key to understanding what a service is, where its location and purpose, and to whom it belongs to.
Are there any tools?
In a recent couple of days, I was exploring a tool/framework that could help me with consistent naming of cloud resources issues. And I was nicely surprised to find the Azure Naming Tool v2.
“The Azure Naming Tool was created to help administrators define and manage their naming conventions while providing a simple interface for users to generate a compliant name.”
What is it for?
The tool was developed using a naming pattern based on Microsoft’s best practices. Once an administrator has defined the organizational components, users can use the tool to generate a name for the desired Azure resource.
These recent updates come with globally optional components, multi-type name generation, some style and/or layout updates, and more.
The Azure Naming Tool was designed to be as extendable and functional as possible. In order to accommodate that flexibility, several architectural aspects were implemented.
The ANT team will continue to improve the tool and publish updates to the GitHub repository. All feedback is welcome, and feel free to submit a code change if you have a better idea for any part of the tool. Good luck!
We started the #CloudMarathoner community and cloud learning journey approximately 3.5 years ago with few posts and followers. My main intention in starting this hashtag is to help everyone learn the #cloudcomputing and share training resources that could help you in your awesome #cloud journey.
We continuously GROWING
Thank you for your continued feedback and support! Our community is almost 1400+ members string and we are able to reach and empower more people now.
Many Thanks to each of you, who has #shared and commented on #CloudMarathoner posts on social media.
Thank you.. Thank you… Thank you.. For being a true #cloudmarathoner in learning the #cloud and sharing it with your community!
I would like to welcome everyone who is landed on this page to check out the Azure Spring Clean 2023 event and Learn new cloud skills!
Before kicking off the topic, I would like to start with a “THANK YOU” message for the organizers of the event; especially for Joe, Thomas, and everyone who is involved in making this event a successful experience for everyone!
In the spirit of Azure Spring Clean, we will explore how to organize Azure Security Services using the infrastructure-as-Code (IaC) approach with Azure Bicep.
We will look into how you could declaratively define and deploy your Azure security resources including Azure Policies to tackle real-world business problems. So, get yourself ready for simple yet powerful demos that will turn you into a hero.
And don’t worry, if you are new to Azure Bicep as we will have a super express introduction to this new IaC language to get you started with fundamentals.
Azure Bicep is a new declarative Domain Specific Language (DSL) for provisioning Azure resources. The purpose of Azure Bicep is to simplify the resource creation and management experience with a cleaner syntax and more code reuse.
Declaring resources as IaC
There are many benefits in declaring and managing cloud infrastructure resources as a code. It provides benefits, such as increased compliance, visibility, controlled deployments and versioning of changes that get deployed into your cloud environments.
The following screenshot demonstrates how Azure Bicep declares cloud resources on the left side of the panel:
Organizing cloud resources
No matter how small or big is your project, taking time to think through the approach of how to organize your digital assets is an important task. In Microsoft Azure, you would need to consider a couple of points while trying to make this decision. Namely, you would need to consider the following factors:
Resource Governance approach
IaC management options
Modules, ACR, Template Specs, etc.
Azure Policies for governance
The Azure Policies are assigned with a unique mission to guard the compliance aspect of your cloud resources and workloads. It evaluates resources at specific times (by default happens every 24 hours) during the resource lifecycle changes and the policy assignment lifecycle updates.
Thus, whenever you get a resource created, updated, or deleted within a scope of the monitored compliance, or if you update/create an Azure policy then the compliance evaluation cycle will determine the compliance of these changes by auditing, blocking, or allowing the action to be performed.
Securing storage account options
Note: this section of the post is in progress… It will be presented with the screenshots and GitHub repo for you. Stay tuned, and check in a few days 😉
video & Demo – a sweet combo
In the video below, I briefly cover the posted information in this blog post which also includes the instructions on how to run the demo and get the scripts to deploy Azure Policies for your Tag Governance scenario.
Without any overdue, here is the video that should be available to you:
The following image is a screenshot from the slide that demonstrates the Bicep code that declares the policy definition and initiative, with the final view of deployment on the Azure portal.
Thank you so much for reading this post and learning about Azure security and compliance and how IaC language Azure Bicep can help you in this journey. This is a bit different perspective to strengthen your resource/workload compliance on Azure using IaC approach.
Please, keep up the good work by securing your organizational and customer cloud environments!
I have been getting a strange error on the Azure Bicep Insert functionality on my laptop, while it was working as expected on my work laptop.
Thus, I started to compare Azure Bicep versions and extension plugin versions on VS Code. Even though, both have the same versions, I was getting the following errors:
ChainedTokenCredential failed due to an unhandled exception
“Caught exception fetching resource: The ChainedTokenCredential failed due to an unhandled exception: Azure CLI authentication failed due to an unknown error. See the troubleshooting guide for more information.”
After a couple of hours of troubleshooting, I was getting a different error:
“Caught exception fetching resource: The ChainedTokenCredential failed due to an unhandled exception: Azure PowerShell authentication failed due to an unknown error. See the troubleshooting guide for more information.”
I am really excited and happy to see my session is accepted ✅ for this year’s #AzureSpringClean2023 event 🎉
What is Azure Spring Clean?
The Azure Spring Clean 2023 is an event that promotes well-managed Azure tenants. In order to achieve this goal, organizers encourage the cloud community professionals to create articles that highlight best-practices, and lessons learned, and help with some of the more difficult topics of Azure Management.
Join me this March, to learn and explore 🔍 how to organize Azure Security Services using the IaC approach with Azure Bicep.
We will look into how you could declaratively define and deploy your Azure security resources including Azure Policies to tackle real-world business problems. Thus, get yourself ready for simple yet powerful demos that will turn you into a hero.
I would highly encourage everyone to join this event and learn best practices on Azure this spring!