Microsoft Azure App Service Reviews

We use this solution in a very large number of areas, such as for functional apps, web apps, to trigger HTTP requests, for web API integration. This solution has a vast array of features.

The feature I find most valuable is the 'Diagnose and Solve problem' function. This not only allows us to fix a problem, but also to generate analytics on why the issue occurred.

I also find the application insight feature to be essential for use in our production environment.

I would like to see some improvement in the UI/UX design, to make navigation of this solution more user friendly. For example, it could contain more explicit information on each of the features.

There should also be some development on the architectural flow of this product, to show application dependencies across the network. This would help with fixing issues that may impact other areas.

We have been using this solution for four years.

We have found this to be a fairly stable solution so far.

This is an easily scalable solution.

The technical support for this product is very good, with SLA's provided for when issues are raised. There is also a lot of online support available through the Microsoft community pages, forums, and downloadable guides.

Positive

The initial setup of this solution isn't complex, but it is time consuming. There is a lot of documentation to go through before implementing this solution, to ensure that it is fit for purpose once deployed.

The pricing for this solution is set in tiers, with the overall cost depending on the features that are required. I would advise organizations to have a detailed look at the functions they need, to ensure that they are in the correct pricing tier.

I would rate this solution 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 have used App Services to integrate a lot of solutions, to bring content from a different domain or maybe a different data source. 

We were using a lot of Microsoft Azure services to build. We were also leveraged to deploy non-SAP solutions like Python Machine Learning IOTs, using these App Services to bring solutions into SAP.

We were doing one POC for one of the last customers where we had to integrate mobile solutions and IoT. We were using App Services to build those IOT components, retrieve data, and integrate with SAP.

We were using some temperature readings for our supply chain logistics company. Once we read temperatures, we'll push it to the App Service, and App Service will internally push it to the digital twins. From there, we get the events and consume those events into a function, and then whatever the functions read will be pushed into the DB.

The best feature is the latency is significantly less. The functions which are provided in this App Services app work very fast, and there are no latencies that we see. The realistic data allow us to configure analytics on top of it, and it is very fast.

It is easy to set up.

The cost is reasonable.

We've found the product to be stable. 

Recently, we have used some scheduling and event management. From an IoT use case perspective, we're all good, however, we should have additional plugins.

We started using the solution in 2021.

It is stable so far. We have not received any challenges during our implementation. 

Azure was very fast in doing scalability from a user management perspective. Whenever you add a new user, it automatically aligns, and then the license gets adjusted automatically.

We have a few thousand users. Pretty much everyone uses it. 

We began using the solution due to the fact that digitalization is becoming normal now, and we have to integrate a lot of non-SAP solutions. App Services gives a lot of flexibility for us to bring data from any data source and push it to enterprise services, which we want to consume.

The solution is easy to set up. It's very easy. it's not complex at all. 

It only takes about a week to deploy a bare-bones product. To have an end-to-end solution, it only takes 20 to 30 days. 

From a licensing cost perspective, Microsoft Azure, compared to other cloud services providers, is competitive and reasonable from an implementation point of view.

The Azure license is based on usage. It's pay as you. We pay for what we consume. 

We are partners with Microsoft.

I'm not sure what version of the solution we're using. 

I'd advise users to try out the product.

I would rate it eight out of ten. It is flexible and easy to use. Configuring and deploying are also quick and easy. 

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.

We use this solution for everything I do. We use it on e-commerce platforms and for business activities. Currently, we're using the latest version of the App. However, we used the e-commerce version between 2019 and 2020.

The most valuable feature is the Power Apps because it is very user-friendly. In comparison, the Logic Apps and Azure functions are very robust.

I can't pinpoint a specific feature that can be included in the next release because Microsoft is making new changes to the app every day. Currently, everything works perfectly. 

We have been using this solution for five years. I am a Cloud Solution Architect with TCS, primarily on the Azure front. I research different types of Power Apps. I focus on POCs and deal with architecture data.

This solution is stable as we haven't faced problems working with it yet.

This solution is scalable.

I can't comment on my experience with the customer service and support team because we connect directly with Microsoft whenever we have any issues.

Positive

It is easy to set up if you have experience and knowledge working with it, but the setup is complex if you have no experience. 

Regarding pricing, I can't comment on pricing because I don't deal with issues related to pricing. 

I rate this solution an eight out of ten. My advice would be to gain experience, get an MSN license and practice before working in production environments.

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.

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 use Azure App Service for both app development and deployment. Sometimes, we use it for testing, and we also have several products running in production on the platform.

One valuable feature of Azure App Service for us is its integration with Azure DevOps, which we heavily rely on in our development process. It is user-friendly once you understand how it works, although getting to that point can be a challenge. Additionally, Azure App Service offers excellent integration with Microsoft infrastructure and developer solutions.

In terms of improvement, the technical support could be better.

I have been working with Microsoft Azure App Service for almost six years.

We have faced reliability issues due to configuration issues on our end, not the technology itself. While Azure App Service provides information on problems, sometimes it is not sufficient, and resolving issues can be time-consuming.

In terms of scalability, we haven't encountered any issues with Azure App Service. 

The support I have received, mostly from individuals in India, hasn't been very helpful. They tend to send long emails with lots of links, which often don't directly address my specific issue. This can be frustrating and time-consuming, as it doesn't efficiently solve the problem at hand. Azure App Service might offer better support with higher-priced plans, but those might be too costly for smaller external companies like ours. I would rate the support as a three out of ten.

Negative

I have used SolarWinds along with Azure App Service for web application development.

Installing Azure App Service has been challenging at times. Whether deploying through Azure pipelines or directly from Azure, the process can be time-consuming due to configuration complexities. We have encountered instances where resolving issues took days or even two to three weeks to complete the deployment.

Microsoft offers various pricing plans and licensing options, which initially seem reasonable, especially for small companies like ours. However, as we grow, the pricing can become less flexible. We pay for Azure monthly, while some licenses, like the Action Pack, are paid annually.

Overall, I would rate Azure App Service as an eight out of ten. It is a good tool but could be more user-friendly.