Microsoft Azure App Service Reviews

The most valuable features of Microsoft Azure App Service are its vertical and horizontal scaling, along with its ability to throw a docker image.

Microsoft Azure App Service needs some improvement in the scaling area. The solution should also be able to easily host apps that don't have an HTML front end.

I have been using Microsoft Azure App Service for ten years.

I rate Microsoft Azure App Service ten out of ten for stability.

Around 1,000 users use Microsoft Azure App Service in our organization.

I rate Microsoft Azure App Service a nine out of ten for scalability.

The solution's initial setup is pretty simple. I rate Microsoft Azure App Service an eight out of ten for the ease of its initial setup.

Microsoft Azure App Service's deployment is very quick and could take minutes since it is on an app-by-app basis. The solution's deployment requires minimal staff.

I rate Microsoft Azure App Service a seven out of ten for pricing.

Before choosing Microsoft Azure App Service, we evaluated AWS. Ultimately, we decided to go with Microsoft Azure App Service because it natively works much better with dot net applications than AWS. Not that AWS does it badly, but Microsoft Azure App Service is much more up-to-date.

Microsoft Azure App Service is deployed on-cloud in our organization.

I advise users to think about the types of applications they want to host on the cloud and adapt it for the cloud instead of doing a lift and shift.

Overall, I rate Microsoft Azure App Service an eight out of ten.

We are using Microsoft Azure App Service in systems, such as government, credit loan, and app services.

The most valuable feature of Microsoft Azure App Service is autoscaling and resource grouping. Additionally, the integration works well, it is easy to do.

Microsoft Azure App Service has a lot of complexity because there are a lot of options and functionality. It is simple to become confused, there are many technical elements to learn before you can utilize the solution. If they could make the solution easier to use it would be a benefit. 

In an upcoming release, mobile device usage could be a better experience.

I have been using Microsoft Azure App Service for approximately five years.

The solution is highly stable.

I rate the stability of Microsoft Azure App Service a ten out of ten.

With all the deployments we have in many companies there are only a few users that use it.

I rate the scalability of Microsoft Azure App Service a nine out of ten.

The initial setup of Microsoft Azure App Service is simple. 

The price of the support could improve. It is expensive.

I rate the price from Microsoft Azure App Service a one out of ten.

I did compare this solution with Amazon AWS and Amazon and Amazon EC2. They are all comparable solutions. What stands out the most in Microsoft Azure App Service is the speed. Selecting the best solution will also depend on the use case.

We utilize Azure Cosmos DB, which has a distinct architecture compared to other services. Initially, we were concerned about the high costs associated with it since every document incurs charges due to Azure's containerization of every collection. However, we discovered that running it in a single container eliminates this cost.

I rate Microsoft Azure App Service a nine out of ten.

We're working on the premium, dynamic, and standard price sharing on Microsoft Azure App Service, and most of our APIs are hosted on Microsoft Azure App Service. We're also using the platform for API calls and security management.

We're not currently using Microsoft Azure App Service for any static web. We have a lot of API calls daily that try to access services because our applications are interconnected with either Coupa or Microsoft Dynamics 365.

What I found most valuable in Microsoft Azure App Service is that it's a PaaS.

I also like that it supports Docker and multiple frameworks so that you can work on Java, Ruby on Rails, PHP, and Python.

Another valuable feature of Microsoft Azure App Service is DevOps optimization.

The platform also has connectors and supports on-premise servers, including the IIS server. Microsoft Azure App Service is helpful when my company needs to do some API configurations with SaaS and IIS. However, it still depends on the use case.

I also find Microsoft Azure App Service templates valuable because of their compatibility with WordPress, Joomla, and Drupal.

Microsoft Azure App Service also gives you access to the Azure Marketplace, which helps my company work on Azure functions.

I also like that the platform allows you to have a serverless environment for codes you can run from the server side.

I find Microsoft Azure App Service secure, which is another pro. You can go for the newest security protocol version, TLS 1.2 because TLS 1.0 and 1.1 have depreciated. Microsoft Azure App Service lets you efficiently manage security via private and public key certificates.

Overall, my company had an excellent experience with Microsoft Azure App Service regarding serverless configuring, serverless environments for websites, API calls, and microservices.

Limited integration is an area for improvement in Microsoft Azure App Service.

Another area for improvement in the platform is multi-language support. That still needs to be added because, at the moment, my team still has to work on specific Python languages whenever the API calls need to be configured.

The pricing tier for Microsoft Azure App Service also has room for improvement because it significantly varies. For example, you have premium and dynamic pricing, and people on P2 should be offered dynamic pricing or the high-priced tier on offer could still be worked on.

I want a lifecycle pipeline feature, similar to Azure Pipelines from Microsoft Azure App Service. For example, when configuring the pipelines, I should be able to configure the cloud security posture for a specific deployment. By default, there should be a prebuilt cloud security option that can be configured before moving into the production environment.

Microsoft Azure App Service should also give you a clue regarding the risks. It would be best if you didn't have to connect to other modules because that wouldn't be as beneficial to platform users, mainly because Microsoft Azure App Service has a lot of security development kits.

We've been working with Microsoft Azure App Service for three to four years. We're still using it.

Microsoft Azure App Service is a PaaS, so it's pretty stable.

In the past three or four years, my company deployed it with Coupa and Microsoft Dynamics 365, yet I haven't seen any outages.

Microsoft Azure App Service is a Microsoft service, so it has 99.99% stability. I haven't seen any service-related issues from it.

Microsoft Azure App Service is scalable, so if you want to utilize it more, you can go for the recommended price tier. What's best about the platform cost-wise is its detection feature, which tells you if your utilization isn't high in terms of memory, so that advisory helps you manage cost. You'll get a recommendation on which Microsoft Azure App Service module to use.

You'll also find it easy to decide whether to scale up or down for the production or if you need to create an isolated environment.

My company is a gold customer of Microsoft Azure App Service, so Microsoft provides premium technical support. It depends on the issue. For example, if my team has a P1 problem, support will call immediately. The support provided is similar to Cisco Smart Net, where support is very supportive, and it's especially recommended if you have a critical issue and your environment is down.

Apart from Microsoft Azure App Service, my company also uses the AWS serverless API solution, Amazon API Gateway, where microservices and risk APIs run. It's used side by side with Microsoft Azure App Service. As I belong to the security team, I'd always prefer Microsoft Azure App Service because it's pretty systematic, and Microsoft does checks and balances.

If you go for Amazon API Gateway, it's cheap and can give you different configurations. However, it's pretty tricky, security-wise, because you still have to enable a couple of new services for security. You cannot manage security easily on Amazon API Gateway. You still have to configure Security Hub and GuardDuty. It's tricky regarding security and data ingestion of logs because you still need to send that to Amazon CloudWatch directly.

I'm not as comfortable with Amazon API Gateway, which is another reason I prefer Microsoft Azure App Service; However, Microsoft Azure App Service is expensive, but I understand that because of its structure, schematics, easy management, and better security. It's secure by default with security-by-design parameters, and Microsoft would manage significant areas.

The initial setup for Microsoft Azure App Service isn't that complex, but it still depends on experience. It's a basic deployment where you define the subscription and the resources you need to connect, depending on how you connect further. For example, you need to configure the code or container or contain it as a static web. Then, you can choose operating systems, such as Linux or Windows, and select the region.

If you need to connect Microsoft Azure App Service to the GitHub repositories for DevOps, you can also connect it. It would be best if you then defined the networks, the monitoring, and the tags. You also define your application insights. For example, it could be a crown jewel app you will configure. You can also configure the detection, and the process is also straightforward to define, security-wise.

Microsoft Azure App Service is an expensive platform, but it depends on the data ingestion. There's a pay-as-you-go plan and a savings plan for compute, but total costs depend on data ingestion and disk space.

For high performance, security, and isolation, Microsoft offers a disk space of 1 TB, with a pay-as-you-go price of $40 per hour, if I'm not mistaken, but that could be lower depending on your key account manager if I remember correctly.

You have options cost-wise. You either go with the standard service plan or the premium plan for Microsoft Azure App Service. If you go for the premium plan, it's expensive, but it depends on your risk appetite.

If you go for Amazon API Gateway or AWS, it would be cheaper, but what's your risk appetite, security-wise? You can still enjoy security from AWS, but that means enabling six modules, for example, Security Hub, GuardDuty, etc. Then, for data log ingestion, you still need to enable Amazon Kinesis Data Firehose, so that would make the costs more expensive.

In comparison, you can go for the premium Microsoft Azure App Service plan and enable the platform and services. The data will automatically be adjusted toward your Microsoft Sentinel account. You also don't need to procure Microsoft Defender for Cloud because, by default, Microsoft provides security.

Going for Microsoft Azure App Service also means that Microsoft Azure will also manage identity protection.

I'm working on Microsoft Azure App Service, end-to-end security such as Amazon GuardDuty, and AWS Security Hub.

My company uses SQL services, AWS RDS, PaaS, and SaaS.

My team also works on all Microsoft Defender for Cloud, Azure WAF, Azure Network Watcher, and Azure Service Map modules.

My company works on endpoint security and related solutions, such as Microsoft Purview Compliance Manager and Microsoft Purview DLP.

Microsoft Azure App Service is a mobile development platform. It's a serverless environment.

My company has an interconnection with Microsoft Azure App Service, with API calls coming from the platform, so there's no specific user but a service account used by the company.

My rating for Microsoft Azure App Service is seven out of ten based on the features used within the company.

My company is a customer of Microsoft Azure App Service.

It simplifies the deployment of applications, including those built with technologies like .NET or UCS, making it particularly valuable for microservices applications. It streamlines the deployment process, allowing developers to easily deploy and manage their applications without requiring dedicated DevOps engineers.

The primary and standout feature is ease of deployment.

Having a surplus of tutorials from Microsoft, rather than relying solely on documentation or features from other sources like YouTube, can be beneficial.

It offers excellent stability capabilities.

It offers configurability through the Azure portal. Adjusting resources such as CPU or memory is a straightforward process, making it easy to scale up or down based on your requirements. We manage multiple projects. Each project, whether it's a toll-free initiative or any other, typically involves three or four developers who contribute to the content and development processes.

Deployment is a straightforward process: after coding, you package the application into a folder, compress it into a ZIP file, and execute a command line with the ZIP file's path. This command includes the ZIP file's location, and Azure App Service takes care of running the application and exposing it without any further complexities. I can handle the deployment on my own.

The cost is reasonable.

Overall, I would rate it eight out of ten.

I use this solution to learn about the application development technology and platform and be able to recommend it to my employer.

I'ts not being used yet.

I particularly appreciate that this is a very straightforward and easy solution to use.

I would like to see some significant improvement in the technical support provision for this solution. 

I have been working with this solution for around six months.

I have found this to be a mostly stable solution during my time using it.

This is a very easily scalable solution with practically unlimited growth potential.

The technical support for this solution is terrible.  I regularly experience delays in response times when I raise and issue, and have often had occasions when no response at all has been given.

Negative

The initial setup of this solution is very straightforward.

I implemented this solution myself, as it is for personal use.

I would recommend that potential users of this solution enroll in some kind of formal training, perhaps from a Microsoft partner. They should also be prepared to keep up with the regular changes applied to this platform.

I would rate this solution an eight out of ten.

We are a reseller of Microsoft services and deliver this product to our customers. 

It is for hosting web and mobile applications and data. When we are integrating different applications, we need to connect them with Microsoft Azure services for integration.

We like that it's a close environment where we can do a lot of things. It integrates well across Microsoft products. 

It's stable. Microsoft recently announced it will be adding a local cloud into the UAE.

The solution can scale.

They need to be more transparent in terms of the scalability of the product. It's not clear how many users can use it in tandem. The non-functional information about the platform should also be readily available. 

Unlike AWS, which has many offerings, Microsoft's choices are more limited. AWS also has manuals and videos in order to clarify how things work. Microsoft needs more of that. 

Jordan and Saudi Arabia do not yet have local in-country clouds. 

The solution is somewhat expensive. They have a lot of competition from open-source rivals and need to make their offering more competitive somehow. 

My background is in Microsoft technology, and I have been working with Microsft for five years and with this particular solution for almost three years. 

It's extremely stable and reliable. There are no bugs or glitches, and it doesn't crash or freeze. 

We haven't had any issues with scaling just yet. I haven't hit any limitations. We work with both SMEs and enterprises, and it has met the needs of both. 

I handle pre-sales of software and therefore do not deal with technical support. 

It is moderately easy to deploy. A company would require some technical help or know-how. There's maybe 50% complexity in general. Half is hard, half is easy. 

Our support team is able to assist clients in setting up the solution. 

The price is relatively high compared to other platforms. I can't speak to the exact pricing, however. 

There may be some ancillary services that may cost more. They don't have a comprehensive plan, yet they charge for everything. 

We're a partner.

I'd rate the solution eight out of ten. 

Microsoft Azure App Service is primarily used to host web-based applications.

Microsoft Azure App Service could improve by having better integration with on-premise solutions.

I have been using Microsoft Azure App Service for approximately five years.

The stability of Microsoft Azure App Service is good.

Microsoft Azure App Service is scalable.

We have customers with 20,000 employees and others with 100,000 employees using this solution.

The support from Microsoft Azure App Service has been supporting my clients.

The setup of Microsoft Azure App Service is easy. The Microsoft Azure App Service can be created within seconds.

The cost of the solution is based on usage. It is less expensive than other solutions.

I would recommend this solution to others.

I rate Microsoft Azure App Service a ten out of ten.

My use case for Microsoft Azure App Service is to deploy web solutions faster and easier online. Rather than setting up my servers and worrying about the need to set up the infrastructure, the OS, and the run time, I use Microsoft Azure App Service for faster deployment and to get my solutions to the market at a faster rate.

I've used Microsoft Azure App Service quite a lot, and what I like best about it is that it's a serverless HAM, which is a feature that can run a function, a single function, but faster and more frequently without needing any other assistance. This has been what I found most valuable in Microsoft Azure App Service, the serverless option that's very easy to utilize, and you only need a minimal setup to use this and to enjoy the functionalities required, so the solution gives me a lot of comfort whenever I'm using it.

Customers love it when a solution is affordable, but with Microsoft Azure App Service, you can start and stop it, and when you stop it, it won't be reachable and it won't be available, yet you're still being charged for it.

You'll still be charged even if the solution isn't accessible because Microsoft Azure App Service runs on a shared virtual machine that keeps on running, so if there's a way to work this out, it'll be a great improvement to only pay for what you use. The solution should have no hidden cost and no extra charge when it's stopped. This is what needs improvement in Microsoft Azure App Service.

I've been using Microsoft Azure App Service for four years now, but professionally, this is my second year to use it.

Microsoft lives up to its word. For example, the SLA it promised is 99.7%, and to the best of my knowledge, Microsoft Azure App Service has been able to reach that percentage without any global outage from any of the services and underlying infrastructure that power it. The solution is available 100% throughout its lifetime.

Microsoft Azure App Service is very scalable, and it's built in such a way that it encourages flexibility in scaling. You can grow from a single instance to thirty instances, and you can increase from 5GB RAM to over 30GB RAM.

Microsoft Azure App Service is designed so you can start small and expand as your customer base grows. It's built around that ideology and it's been living up to that ideology. The solution is defined scalability-wise, and it's practical in both approach and usage.

The setup for Microsoft Azure App Service is very straightforward. All you have to do is navigate to the portal, search for the App Services, curate one, give it a name, select a location, region, and resource group, then customize the number of RAM you want. Do you want a disk to be attached to it? Do you want to do some modern networking parameters which are not requirements?

The basic requirements for setting up Microsoft Azure App Service are very straightforward, so anyone who can power his computer can get started with.

You also have several deployment options to choose from for Microsoft Azure App Service which would make life easy. You can deploy from your existing repository, or you can upload your code directly, so for me, the setup is quite easy for the solution.

How long Microsoft Azure App Service deployment usually takes depends on the content, specifically the size of the content you want to deploy to it. At most, if you have a one-page website, the solution takes less than five minutes to deploy, which is quite fast, so you can get your sites up and running in less than twenty minutes with the setup and deployment, so the process is considerably okay.

The pricing for Microsoft Azure App Service is per hour, and you're billed per hour, and it depends on the plan you're using. Each plan can host up to a minimum of four to eight applications at a time, so the pricing is quite okay with how I use Microsoft Azure App Service currently, but with the little testing I've done, I saw that some other regions tend to be costlier than others. If the same SLE is delivered for all services, there should be a way to make the prices parallel across regions. Having more transparent pricing for Microsoft Azure App Service would give customers more comfort.

Microsoft Azure App Service can be used by a lot of people, but either the cloud engineer or the infrastructure engineer should be in charge of it because the solution relates to a lot of infrastructures and other resources such as storage, databases, networking, firewalls, and it can even relate to APIs and other resources outside the cloud environment. A lot of people can work on Microsoft Azure App Service, but it's best handled by the cloud engineer who has an understanding of how to implement the relationship with other resources.

I've worked on Microsoft Azure App Service for four years, and I have enough experience to orchestrate, manage, and maintain it.

My advice to anyone looking to use Microsoft Azure App Service is that you should try it and see the power of getting your applications out at a faster rate. It can get your application to speed up in less than twenty minutes, and it can handle between thirty to fifty thousand users at a time. You can try Microsoft Azure App Service while you're starting, then you can keep scaling until you need more resources or more solutions that can help you with your workload. Try Microsoft Azure App Service out, so you can see for yourself what it can give you. This is the best way to enjoy its features and benefits.

My rating for Microsoft Azure App Service is nine out of ten.

My company is a partner of Microsoft Azure App Service.