Microsoft Azure is a cloud computing platform and infrastructure for building, deploying, and managing applications and services through a global network of Microsoft-managed datacenters.
$29
per month
Red Hat OpenShift
Score 9.3 out of 10
N/A
OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.
N/A
Pricing
Microsoft Azure
Red Hat OpenShift
Editions & Modules
Developer
$29
per month
Standard
$100
per month
Professional Direct
$1000
per month
Basic
Free
per month
No answers on this topic
Offerings
Pricing Offerings
Microsoft Azure
Red Hat OpenShift
Free Trial
Yes
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
The free tier lets users have access to a variety of services free for 12 months with limited usage after making an Azure account.
—
More Pricing Information
Community Pulse
Microsoft Azure
Red Hat OpenShift
Features
Microsoft Azure
Red Hat OpenShift
Infrastructure-as-a-Service (IaaS)
Comparison of Infrastructure-as-a-Service (IaaS) features of Product A and Product B
Microsoft Azure
8.5
Ratings
6% above category average
Red Hat OpenShift
-
Ratings
Service-level Agreement (SLA) uptime
9.00 Ratings
00 Ratings
Dynamic scaling
8.00 Ratings
00 Ratings
Elastic load balancing
9.00 Ratings
00 Ratings
Pre-configured templates
8.00 Ratings
00 Ratings
Monitoring tools
8.40 Ratings
00 Ratings
Pre-defined machine images
8.00 Ratings
00 Ratings
Operating system support
8.90 Ratings
00 Ratings
Security controls
9.00 Ratings
00 Ratings
Automation
8.00 Ratings
00 Ratings
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
Actually, migrating to Microsoft Azure is a good solution for almost any situation, especially when all components of your network are ready to become cloud-based. The only drawback I personally encounter frequently is that older software packages cannot always be easily picked up and moved to Microsoft Azure in an optimal manner.
Red Hat OpenShift, despite its complexity and overhead, remains the most complete and enterprise-ready Kubernetes platform available. It excels in research projects like ours, where we need robust CI/CD, GPU scheduling, and tight integration with tools like Jupyter, OpenDataHub, and Quiskit. Its security, scalability, and operator ecosystem make it ideal for experimental and production-grade AI workloads. However, for simpler general hosting tasks—such as serving static websites or lightweight backend services—we find traditional VMs, Docker, or LXD more practical and resource-efficient. Red Hat OpenShift shines in complex, container-native workflows, but can be overkill for basic infrastructure needs.
Azure simply provides end to end life cycle. Starting from the development to automated deployment, you will find [a] bunch of options. Custom hook-points allow [integration] on-premise resources as well.
Excellent documentation around all the services make it really easy for any novice. Overall support by [the] community and Azure Technical team is exceptional.
BOT Services, Computer Vision services, ML frameworks provide excellent results as compare to similar services provided by other giants in the same space.
Azure data services provide excellent support to ingest data from different sources, ETL, and consumption of data for BI purpose.
One thing is the way how it works with the GitHubs model on an enterprise business, how the hub and spoke topology works. Hub cluster topology works the way how there is a governance model to enforce policies. The R back models, the Red Hat OpenShift virtualization that supports the cube board and developer workspace is one big feature within. So yes, these are all some features I would call out.
In our experience, Azure Kubernetes Survice was difficult to set up, which is why we used Kubernetes on top of VMs.
Azure REST API is a bit difficult to use, which made it difficult for us to automate our interactions with Azure.
Azure's Web UI does a good job of showing metrics on individual VMs, but it would be great if there was a way to show certain metrics from multiple VMs on one dashboard. For example, hard drive usage on our database VMs.
So I don't know that this is a specific disadvantage for Red Hat OpenShift. It's a challenge for anything that Kubernetes face is. There's an extremely large learning curve associated with it and once you get to the point where you're comfortable with it, it's really not bad. But beating that learning curve is a challenge. I've done a couple presentations on our implementation of Red Hat OpenShift at various conferences and one of the slides I always have in there is a tweet from years ago that said, "I tried to teach somebody Kubernetes once. Now neither of us knows what it is."
We have been very satisfied with Windows Azure and now a lot of our business depends on it as more teams are now deploying their applications into Azure. Our next step is to have our Infrastructure team move their resources to Azure. It will take awhile for that to happen but we are positive that it will.
This is the current strategy for the company, most of the products in the organisation are aligning to Openshift and various use cases it support. Also lot of applications are being developed for AI use case, openshift.AI provides opportunity to host and leverage the AI capabilities for these applications
Microsoft Azure's overall usability has been better than expected. Often times vendors promise the world, only to leave you with a run-down town. Not the case with our experience. From an implementation perspective, all went perfect, and from the user-facing experience we have had no technical issues, just some learning curve issues that are more about "why" than "how"
The virtualization part takes some getting used to it you are coming from a more traditional hypervisor. Customization options are not intuitive to these users. The process should be more clear. Perhaps a guide to Openshift Virtualization for users of RHV, VMware, etc. would ease this transition into the new platform
Redhat openshift is generally reliable and available platform, it ensures high availability for most the situations. in fact the product where we put openshift in a box, we ensure that the availability is also happening at node and network level and also at storage level, so some of the factors that are outside of Openshift realm are also working in HA manner.
Overall, this platform is beneficial. The only downsides we have encountered have been with pods that occasionally hang. This results in resources being dedicated to dead or zombie pods. Over time, these wasted resources occasionally cause us issues, and we have had difficulty monitoring these pods. However, this issue does not overshadow the benefits we get from Openshift.
Support is easy with all the knowledge base articles available for free on the web. Plus, if you have a preferred status you can leverage their concierge support to get rapid response. Sometimes they’ll bounce you around a lot to get you to the right person, but they are quite responsive (especially when you are paying for the service). Many of the older Microsoft skills are also transferable from old-school on-prem to Azure-based virtual interfaces.
Every time we need to get support all the Red Hat team move forward looking to solve the problem. Sometimes this was not easy and requires the scalation to product team, and we always get a response. Most of the minor issues were solved with the information from access.redhat.com
I was not involved in the in person training, so i can not answer this question, but the team in my org worked directly with Openshift and able to get the in person training done easily, i did not hear problem or complain in this space, so i hope things happen seamlessly without any issue.
We went thru the training material on RH webesite, i think its very descriptive and the handson lab sesssions are very useful. It would be good to create more short duration videos covering one single aspect of openshift, this wll keep the interest and also it breaks down the complexity to reasonable chunks.
As I have mentioned before the issue with my Oracle Mismatch Version issues that have put a delay on moving one of my platforms will justify my 7 rating.
I feel that Microsoft Azure typically outperforms Google Cloud Platform in hybrid cloud capabilities, integration aspects, and, primarily, security compliance features. Azure offered superior integration with Microsoft's enterprise software ecosystem, and it's second to none in my opinion. This made it the natural choice for most, especially if heavily invested in Windows, Office 365, or Active Directory deployments. We chose Azure over GCP because we simply needed Windows workload support as a strong driver, more access to global regions, and let's not forget that most tech teams in an organization are Microsoft Certified, which makes skillset transfer from on-prem to cloud a minimal learning curve over shifting to a different provider.
We utilized the Thycotic Secret Service to manage all our application secrets, resulting in seamless integration with our applications. We developed all the applications using Red Hat Fuse (currently migrated to Quarkus). We used the built-in Kali Linux support of OpenShift to manage and configure the services and API. Additionally, the Red Hat Developer Studio facilitates faster development.
This is a great platform to deployment container applications designed for multiple use cases. Its reasonably scalable platform, that can host multiple instances of applications, which can seamlessly handle the node and pod failure, if they are configured properly. There should be some scalability best practices guide would be very useful
Times and growth went into it. By balancing on-premises maintenance with continuous cloud improvements, we’ve budgeted and planned endlessly increased capacity.
In today’s world of cyber-crime, clients can put even more faith in what they’ve heard. We built an innovative single-sign-on hub for all users. Also, other business platforms use Azure application gateways, reducing worker switching time and increasing productivity.
Its step can automate to improve the investment. In addition, we can integrate our organization’s credentials into an authorization for other systems.
It has allowed us to see where we need to be in the container world. I'm going to call it a net neutral impact, not negative or positive. It has given us a sense of what we are ready for and what we're not ready for. You know where you stand.
You don't know what you don't know, so it helps us know what we want to know.