What is our primary use case?
Azure is utilized to facilitate computing needs for our clients' sites. Most often, it's employed to enable them to host their products in the cloud, manage disaster recovery, conduct backups, and host applications. Additionally, for clients with on-premise infrastructure, Azure serves to replicate that setup in the cloud. We offer Azure-based solutions to fulfill these requirements and seamlessly provide access to them, typically through domain access, after setting up payment arrangements.
How has it helped my organization?
Azure integration became crucial for a business facing cost-saving challenges. They were burdened by the physical space and maintenance costs of on-premise infrastructure. Additionally, issues like electricity outages prompted them to consider migrating certain infrastructure components to the cloud. This move aimed to alleviate space constraints, reduce maintenance expenses, and enhance reliability, potentially enabling them to divest part of their infrastructure in the future.
The scalability features of Azure had a significant impact on projects for our customers, particularly in one instance where a deal was lost due to scalability issues. This challenge doesn't necessarily stem from Azure itself but rather from the complexity of migrating third-party dependencies to the Azure environment. Often, the lack of proper documentation and understanding of how these dependencies were originally implemented poses obstacles.
What is most valuable?
Azure is highly valuable due to its cloud-based nature, which reduces the need for extensive hardware purchases and server maintenance costs. It serves as a quick and convenient solution for spinning up VMs, creating websites, and making businesses visible online. The platform's user-friendliness eliminates the need for lengthy training periods, enabling swift navigation for new users. Companies can easily onboard new personnel by providing them with relevant documents, allowing them to quickly grasp how to manage resources and create necessary components on Azure.
Azure Arc is incredibly valuable because it allows businesses to connect and secure their resources, regardless of where they are hosted. This means that even if they are using other cloud platforms like AWS or have on-premise infrastructure, they can still benefit from Azure's features. With Azure Arc, businesses can have centralized management and security across their entire environment, including legacy systems and other cloud providers. While Azure Arc may come with a higher cost, its ability to bridge different platforms and provide enhanced security makes it a compelling option for businesses looking to leverage Azure services without fully migrating their infrastructure.
What needs improvement?
Improvements are needed in Azure to enhance integration tools and support for effectively migrating and managing third-party dependencies. Additionally, there is a significant issue with payment restrictions on Azure, particularly for users in regions with limitations in their local economies. Integrating third-party payment services could alleviate this problem, allowing users from various international locations, such as China, Europe, and Africa, to make payments more seamlessly. By providing alternative payment methods beyond the reliance on US debit cards, Microsoft could greatly improve the usability and accessibility of Azure for users worldwide. There's room for improvement in integrating the Azure Marketplace with the Azure portal. It would be beneficial if users could directly communicate with solution owners or developers through the portal. For instance, if a user encounters challenges while using a particular solution from the marketplace, they could easily send an email, initiate a phone call, or even send an SMS to the solution owner or developer for assistance. This direct communication channel would streamline the troubleshooting process and foster better collaboration between users and solution providers, enhancing the overall user experience.
For how long have I used the solution?
I have been working with it for a year.
What do I think about the stability of the solution?
Azure is highly stable, with only one instance of downtime experienced on a specific website and two occurrences in approximately nine months. Overall, it maintains a commendable level of stability, especially when availability zones are utilized. These zones provide critical redundancy, ensuring resilience against unforeseen events and offering a heightened level of reliability.
What do I think about the scalability of the solution?
Azure's scalability is evident when building and adhering to the appropriate architectural principles. Challenges with scaling typically arise when existing platforms or third-party components are involved, making it difficult to align them for efficient scaling. However, Azure Arc aims to address this issue, though it may incur additional costs, especially at larger scales. While some customers may opt for traditional VM provisioning on Azure due to cost considerations, Azure Arc offers an alternative approach for scalability.
How are customer service and support?
The technical support provided is exceptional, and I am extremely satisfied with it. I would rate it nine out of ten.
How would you rate customer service and support?
How was the initial setup?
The initial setup is straightforward.
What about the implementation team?
The documentation provided by Azure for deployment processes to our customers is excellent. Typically, the process begins with signing NDAs followed by a call with the customer's team to understand their requirements. Once the requirements are clear, we review the architecture and assess the feasibility of replicating it on Azure, especially if migration is involved. Subsequently, we create a scope of work detailing the proposed actions and timelines, which the customer must sign off on. Upon agreement, we set a kickoff date and discussed requirements from the customer's end, such as authorization and authentication. During the project kickoff, we ensure someone is available on the customer's side to prevent breaches or delays. We then proceed with the deployment, moving necessary components and configurations. After completion, we conduct testing and allow the customer time to review the deployment, typically two to three weeks. Upon receiving approval, we finalize the project and obtain payment, usually within a timeframe of five days to two weeks, depending on the project's complexity
Azure's simplicity streamlines deployment, often requiring only five to six resources for larger projects. The specific roles may vary based on the project's needs, encompassing expertise in security, architecture, design, and product management.
In most cases, we inform the customer that we're available round-the-clock for feedback during the initial three months post-deployment. This ensures prompt resolution of any issues beyond their capability. If needed, we offer training for their team members. Additionally, customers have the option to enter into a support contract with us for ongoing assistance. Smaller projects may not necessitate ongoing management, depending on their setup.
What was our ROI?
Our customers often report a positive return on investment with Azure, as it helps them save costs. Whether they were previously on traditional infrastructure or on-premises setups, Azure proves to be beneficial, making it a worthwhile investment for them.
What's my experience with pricing, setup cost, and licensing?
The pricing is relatively high.
What other advice do I have?
I highly recommend Azure, as I use it myself. My advice would be for them to seriously consider it, especially when taking their budget into account. Overall, I would rate it eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner