Skip to main content

Expert Insights

blog

Azure


Reasons to avoid third party portal in front of Azure

I often am asked, “should I put a third party portal in front of my Azure or multi-cloud environment?” They ask for a good reason, they want to achieve control of their cloud environment and help their organization to make good decisions. It often comes from organizations who have a self-service portal in their on-premise environment and want to achieve the same ‘efficiencies’ in their cloud environment. There are a lot of reasons why people go down this route, but it is NOT a good idea. In fact, deploying a portal in front of your public cloud is a common anti-pattern that companies should avoid. Here are some of the reasons to avoid this approach.

Nathan Lasnoski by Nathan Lasnoski

Top 10 Mistakes Companies Make Getting Started with Azure: #3—Assuming Your Cloud Environment Needs to Function Like On-Premises

The last several posts in this series have zeroed in on specific structural and technical pitfalls to avoid when getting started with Azure. In this post, let’s zoom out a bit and consider a mistake that’s more conceptual than it is technical—namely, that switching from an on-premises environment to the cloud will not exactly replicate functions.

Nathan Lasnoski by Nathan Lasnoski

Top 10 Mistakes Companies Make Getting Started with Azure: #6— Over-Intermediating the Cloud UX to Control Deployment

Our last posts covered structuring and securing your Azure environment. Now, we’ll focus on a topic important for its actual use: how strictly to control deployment.
 
What people often do is create a portal between developers and Azure itself. This isn’t surprising, as it’s probably what they have on-premises: a portal that exists between developers and the servers that run the applications.
 

Nathan Lasnoski by Nathan Lasnoski

Top 10 Mistakes Companies Make Getting Started with Azure: #7— Ignoring Identity, RBAC and Conditional Access

Now that your Azure Environment is effectively and properly structured, as noted in our previous post, we come across a slippery slope that must be avoided. Now that it has been created, it needs to be secured. It has become second nature to use a seatbelt, lock doors and assure the area is clear when entering or exiting a vehicle, and we must direct that line of thinking when it comes to employing technology.
 

Nathan Lasnoski by Nathan Lasnoski

Top 10 Mistakes Companies Make Getting Started with Azure: #9— Not retraining or restructuring existing employees

Last time, we covered the need for a company adoption strategy in your Azure implementation journey. Here’s another roadblock you have to get past: your employees’ familiarity with your prior ways of doing things. Implementing changes without taking into consideration the need to retrain and restructure your current work dynamics can easily lead to trouble—or, at the very least, inefficiencies.

Nathan Lasnoski by Nathan Lasnoski