Azure App Service vs Microsoft Azure

• It has options to deploy using CI/CD.
• It has great integration with Azure Devops
• It has all the common runtimes, so we don't need to install softwares.

Read full review

• Azure Functions is the easiest serverless service to work with in my experience. Easy to ship Node.js functions without bundling dependencies.
• Proactive and responsive support. We've worked with most other cloud providers - Amazon, Google, Oracle. Amazon Web Services' customer support is a black hole and their documentation is worthless. Google and Oracle are better, but Azure's support is responsive and their docs are pretty good.
• Azure's Web UI is pretty easy to work with

Read full review

• Jumps between resource sizes can get expensive
• You may wind up putting a lot of eggs in one basket--not necessarily a con but something to keep in mind (most of your data will likely be managed and processed through Microsoft products/services if you fully commit to Azure App Service).
• Learning new technology. If you're moving from on-premises to Azure App Service (or any cloud solutions), you'll likely have to rethink how things are done to achieve the same end results (and/or resources may become expensive quickly).

Read full review

• Could be easier to setup redundancy
• Feels as if there are too many options, bells, and whistles you could add.
• Microsoft Azure functions does not have a "Configure Services" method. Programming Azure functions has a slightly different programming model than does a "normal" API application. I would prefer that the startup process be identical.

Read full review

• It's difficult to find the right APP because one software has number of apps so there's no way to find the official version of an app, so sometimes we need to install APP then find out which is performing well.
• Little expensive.

Read full review

• It has taken a few years of planning and growth (which continue), but we've been able to successfully budget and plan for ever increased capacity by starting first with some Virtual Machines and factoring in on-prem maintenance vs cloud constant improvements. VM (server, compute, networking) costs even out quickly over time and will show savings very soon.
• Because of Azure Application Gateways (which cost very little to set up and maintain), we were able to build a state of the art single-sign-on hub for all of our users and other enterprise platforms (mostly non-Microsoft and non Azure systems), reducing the amount of time to switch among these for workers and increasing overall productivity.
• With Azure Active Directory, we do not need to maintain separate identity systems and can more easily integrate our organizations credentials into authorization for access to other systems.

Read full review