Azure Migration Strategy : A checklist to kick off

I heard much time, also mostly from all side that cloud technology is the future of IT. If your organization isn’t already running critical workloads on a cloud platform (and, if your career isn’t cloud-focused), you’re running the very real risk of being overtaken by nimbler competitors. Cloud enables the consumption of technology services with reduced infras07uctural overhead.
We’ve moved from the age of cloud denial to cloud inevitability when everyone is singing the praises of AWS, Azure, and GCP.  Despite this progress, there’s a very large gap between enthusiasm and execution, between talking about how fantastic cloud platforms are and actually relocating your workloads. Focusing on Azure, let’s take a look at some of the key considerations and best practices that should be foremost in your mind as you move forward.
First thing first  Create a Cloud Center of Excellence CCoE
Finding champions across the organization—beyond IT and from the business—who can help remove barriers and push past inertia.
The AWS article, Key Findings from Cloud Leaders: Why a Cloud Center of Excellence Matters, describes a CCoE as:
“…a cross-functional team of people responsible for developing and managing the cloud s07ategy, governance, and best practices that the rest of the organization can leverage to 07ansform the business using the cloud. The CCoE leads the organization as a whole in cloud adoption, migration, and operations. It may also be called a Cloud Competency Center, Cloud Capability Center, or Cloud Knowledge Center.”
1. In order to start first need to Access your current environment
The key to successfully identifying appropriate projects
Enterprise IT environments are complex. high-profile platforms often support (or create) dependencies that aren’t fully understood.
Before you begin your cloud journey, it’s vital to have a full understanding of your current situation. This is so important (indeed, fundamental) to success that Microsoft details current state analysis (or discovery) as the first stage of migration.
2. Azure Migration Workflow  

Before you can move forward, you have to know where you are. Make discovery of your on-premises resources your first critical job. There are a variety of tools that can help, including the Azure Migrate service.

3. Use security best practices from the beginning 
Understand Azure security best practices and build your solutions with those in mind from the start.



Security shouldn’t be an afterthought. Although Microsoft ensures the security of the Azure platform, it’s your responsibility to ensure that your Azure tenant, and the solutions you build, are properly protected.
This is why it’s essential you understand Azure Role Based Access Con07ol (RBAC) to con07ol access to the Azure portal. Use Azure AD as the identity and access management platform for your applications and solutions and employ Azure Security Center to protect your cloud assets from threats.

Azure AD overview and case identification which feet to your need solution and this critical move in cloud journey. 

A security-focused mindset is essential to the ongoing success of your cloud efforts.
So, let’s review:
  • Create a Cloud Center of Excellence: Build a team composed of people from across the enterprise who represent the full business.
  • Assess and understand your current environment: Know where you are to move to where you want to be.
  • Make security second nature: Secure access to the Azure portal, use Azure AD as your identity and access management solution, and employ the Azure Security Center to protect your cloud assets.
If you follow this checklist, you’ll go a long way moving to Azure.

Comments

Post a Comment

Popular posts from this blog

The request has both SAS authentication scheme and 'Bearer' authorization scheme. Only one scheme should be used

Image
While doing testing after doing a POC on Securing Logic App with Azure Active Directory authentication , where I have put logic app behind APIM and before passing the request to logic app, apim does validation of the token.  I was encountered with an error "The request has both SAS authentication scheme and 'Bearer' authorization  scheme.  Only one scheme should be used." Why it happened After validating the token which is part of the header i.e. Authorization, APIM forwards the request as it is to backend. As  Logic app is configured as  back end , it's url already consist of SAS signature plus the request also has Authorization section and this is the problem. By default every request endpoint on a logic app has a Shared Access Signature (SAS) in the endpoint's URL, which follows this format: https://<request-endpoint-URI>sp=<permissions>sv...
Read more

Getting Started with Logic Apps - AS2

Image
What is AS2? Every enterprise requires some kind of product, service or counselling from another enterprises thus there happens a B2B(business to business) communications, some of the communication is unique whereas most of the communications are common for most of the enterprises e.g., Purchase Order. But every enterprise has there own way(format) of sending the messages, leading to difficult management when number of partners increased.  Considering this the Enterprise leaders decided to have some standards/rules defined across the communication leading to B2B protocol standards which provide guidelines for trading partners to follow when conducting business between enterprises. EDI X12, EDIFACT, TRADACOM etc. AS2 stands for Applicability Statement 2 and is a B2B messaging protocol used to transmit Electronic Data Interchange (EDI)/Business documents from one organization to another. So EDI standards define how to format data and AS2 specifies how to securely transport...
Read more

How to Debug and Trace request in Azure APIM - Portal, Postman, RequestBin

Image
Introduction  APIM is a great option to expose API's with out of box features for applying restrictions, preprocessing, postprocessing etc. You can leverage existing API's,  by importing it and it gets added as a new API with all the operations associated with it. And based on the requirements you  apply policies at the stage/level (Inbound,Backend/Outbound) and you are ready to use the API. Before it is shared, we do some testing to make sure everything is working as per the expectation and this is where Debugging and Tracing request becomes important. APIM does provide a way to Trace a call with the help of  Ocp-Apim-Trace http header. So whichever request/call is to be traced, it needs to include this in header  with the value set to true and it has dependency on another header, so that also needs to be passed i.e.  Ocp-Apim-Subscription-Key Note: The api on which Tracing is to applied , it requires the subscription key to be en...
Read more