4 out of 5.0, Reviewed Dec 7, 2016
Azure has substantially improved from 2015-2016 when we started looking. We are happy with the progress we have made with Azure, but because their service offerings become evolving, it has led to challenges on converting to these new service, for example ARM conversion etc.
4 out of 5.0, Reviewed Dec 6, 2016
scalable options and features constantly coming out. communicates changes well.
Always check your Expressroute options and keep multiple expressroutes up in case of an outage.
The flexibility and agility to et infeastructure up quickly and the option to scale.
Some of the services are not mature. Licensing and billing take a rocket scientist to figure out.
i think someof the aervices come out as bet products instead of mature products.
I would have pushed to understand the Expressroute more and created and more robust connection.
4 out of 5.0, Reviewed Dec 6, 2016
The only issue we have is that we still have some Windows 2003 servers that could not be moved to Azure. But our other datacenters will give us that ability until we upgrade. Right now we just have started moving Dev and QA to Azure.
Have a datacenter assessment done first. That way you can understand the relationship between servers for when it comes time to move them.
The ease of bringing up new servers or services is just incredible.
4 out of 5.0, Reviewed Dec 6, 2016
Third party implementor brought more real world experience and was able to focus better than Microsoft who was more high level and general.
Ensure you have your governance piece workedout early on.
Works as advertised. Fast innovations.
Obvious that they will make cross cloud components difficult.
The vendor is rightyfully well experienced in their tools. But they could be a value add if they had more formailty in there expereince with the components around the tools, like governance, process, tooling, etc.
Business drove the initiative by starting work and activations without infrastructure. It took awhile to right the ship. Infrastructure should take the lead first and bring it to business and partner with business.
4 out of 5.0, Reviewed Dec 5, 2016
A maturing cloud offering that is flexible and meets the majority of our development needs. However, partnering with Microsoft has resulted in more sales presentations than actual partnering. This is true of Microsoft across their technology offerings. There is too much upsell in the partnering effort.
Ensure strategy, governance and a cloud team are fully in place.
Ensure governance was fully in place before moving any workloads.
4 out of 5.0, Reviewed Dec 4, 2016
There were some production deployment issues that required extra support but otherwise there were no problems
Make sure the enterprise agreement is sufficient for the production needs
Fully featured, simple to use and get services running quickly
Some of the build/integration servers lagged behind the infrastructure services
There is nothing I wished the vendor did differently
Adopt a production strategy sooner
5 out of 5.0, Reviewed Nov 30, 2016
Microsoft is always easy to deal with and implementing systems is very easy with their portal, once you understand the termenology.
Dive in, and get started. Once you start with the product it becomes more evedient the value.
Ease of standing up new servers and services. Quick to tear them down also.
They need to better communicate roadmap
I like that they are evolving and changing fast, but I hate that they are changing fast. Sometimes it makes it difficult to finish a mini project because things are changed and you may need to pivot in the middle. They could better communicate their roadmap.
Get teams together earlier in the process of evaluating and roll out.
They can take some time to answer questions, and require service tickets to do. Even MS rep has us open cases for things.
Network connect and vpns are still a challenge, along with routing in hybrid environments.
4 out of 5.0, Reviewed Nov 30, 2016
Azure products are easy to implement and install. Support option was not working at first but Microsoft support team fixed that.
Do your research. All clouds are not the same.
Ease of use and consistency. One tool, one portal, MANY products and services available.
Create customer service teams for initial implementation for all of their products. They are adding so many new products to Azure every month it's hard to keep up. It would be great if Microsoft had a team that could learn my business (non-profit) and help alert me to potentially new services that would benefit our company.
Nothing, the implementation has worked really well for what we needed and where we are at exploring cloud IaaS.
Had 1 problem and they were able to resolve it quickly.
5 out of 5.0, Reviewed Nov 28, 2016
Azure is not as mature as AWS, but I feel its catching up. Since we started evaluating they have added several new features that helped our implementation.
Its time to consider cloud offerings and evaluate for some projects with in the company
Flexibility and view infrastructure as software configuration
Use cloud from begining
3 out of 5.0, Reviewed Nov 17, 2016
Migrations to the cloud are rarely trivial, and it's unrealistic to expect JUST developers or JUST QA or JUST Networking/Security to be automatically seasoned at it. Interanal expertise is critical and hard to find. I think the best way to promote cloud adoption technology at large organizations is to offer cross-training (to at least start with foundational skills). Any way that a vendor can do that (promote trainining; especially in-person when possible), I'm all about that.
Dont be so risk adverse. If you allow all the unknowns of migrating to the cloud prevent all necessary momentum (security concerns, budget planning, fall-back plans, stack support, etc) no-one would ever to the cloud. Risk management is no longer about "how do I prevent all risk from the beginning" but more about, do I have the visibility in place to re-direct when I need to. Go down the crazy path, but just make sure you've got the visibility pivot dramatically and quickly if need be. Waiting for the "safe path" isn't competitive. Going at several paths and running down the one you find is best is much more competitive.
It's relatively accessible
The learning curve
More hands-on support and training. Microsoft isn't the work vendor about it, but again fear of the unknown is the biggest barrier to adoption right now. If Microsoft had trained support staff to embed themselves with development teams and architects to promote critical problem solving in Azure (as consultants for example), we'd be all over that. But those resources are very hard to find.
We'd integrate cloud-expertise imbedded with development teams early on. Allow projects to manifest organically sprint-to-sprint with the embedded environment expertise they need. The approach of teams going to a cloud architect who then goes to a data architect who then go to security is fundametally not working. Cloud infrastructure and it's implications are fundametally entwined with applicaiton development.