Microsoft Azure App Service Reviews

One of our reasons to use the product is its cloud service. Our usage is mainly on the cloud and we like the benefits that we can get from the cloud. You can easily do the literal shift of your application easily. You can jump into the cloud very quickly. 

If you are not using the product properly, then it can cost you a lot of money. Hence, you need to make sure that you choose the services wisely. You need to make sure that you have a budget and have some alerts associated with it. The tool's cost can easily go high if you don't consider these things properly. You need to review your existing subscription.  

I have been working with the product for more than two years. 

The product is quite stable. 

The solution is scalable both vertical and horizontal. You should be specific about the Linux or Windows environment. 

The tool's support is good. Sometimes, you need to make sure of the people who are supporting you. Microsoft support can get delayed easily. You need to be in regular contact with the account managers of your account on the Microsoft side so that you can escalate things. Typically, we don't use support and use it only for production issues which require urgency. 

Neutral

The tool's setup is easy since there is a lot of free documentation from Microsoft available. You need to be part of the training as well. The tool's deployment is super quick and gets completed in five minutes. 

The solution is worth its money. 

I would rate the product's pricing a five out of ten and is subscription based. 

I would rate the product an eight out of ten. I would advise people to go with the trial version since you can use most of the functionality in the trial version. 

Our clients use Microsoft Azure App Service for running their websites. The tool also has Azure Functions, which work in coordination with App Service. Azure Functions and Azure Logic Apps are different objects in Azure, but they all work together. I don't know details about how Microsoft Azure App Service works.

Some of the features I found valuable are auto-scaling, SSL integration, cost-effectiveness, and the certificates provided by Microsoft Azure App Service.

Sizing is an area where Microsoft Azure App Service lacks, so it should be made possible to upscale. When trying to scale up, it has a limitation, specifically an upper limitation. In general, scalability should be improved.

The features we use in Microsoft Azure App Service are thirty percent of the tool's services. There are a lot of other options. There's nothing that I can think of that we wanted to configure or the client wanted that was not there in App Service. Nothing needs to be added to the solution.

I have experience with Microsoft Azure App Service. My company has a partnership with Microsoft. Microsoft Azure App Service doesn't have versions.

Stability-wise, I rate the solution a nine and a half out of ten. The product doesn't have stability problems.

Scalability-wise, I rate the solution an eight out of ten.

Microsoft Azure App Service is used by 200 users in my business. We use the product as a part of medium-sized healthcare businesses.

Support is somewhat of an issue with Microsoft Azure App Service. I rate the support a seven out of ten.

Neutral

As a part of my company's partnership with Microsoft, I was involved in the implementation process of Microsoft Azure App Service.

On a scale of one to ten, where one is the difficult setup phase, and ten is an easy setup phase, I rate the setup phase a nine and a half out of ten. The setup process of Microsoft Azure App Service is relatively easier and less complex.

It took me a couple of days to deploy the solution, including deploying a few solutions.

We had to go through with the development team and the client's team to understand the flow of their application, including the logic, and all other different components, having a dependency on Microsoft Azure App Service for the setup phase. We also had to understand how it would function, and then we had to devise a strategy accordingly. We enabled the firewall and communication since, obviously, the traffic should have to go through a firewall, after which we can configure routing and firewall rules accordingly.

On a scale of one to ten, where one is a low price and ten is a high price, I rate the pricing a five. The product is affordable.

There are no costs in addition to the standard licensing fees.

The prices are dependent on the size of the solution required. If there is a need for auto-scaling, then the charges increase as per the size.

I don't see any con for this solution. The only thing is that if the website is huge, like that of Amazon or Flipkart, where auto-scaling may be considered, causing a need to test if Microsoft Azure App Service can cater to that much workload.

Even with all of its limitations, Microsoft Azure App Service is good.

Overall, I rate the solution a nine out of ten.

We use this solution for small rep services. We are using it currently for three or four small use cases and it is a perfect fit for all of them, which is why we chose it. 

The most valuable features of this solution are the easy deployment, the scalability, and the Azure maintenance.

There is always room for improvement price-wise.

We have been using this solution for about three or four years.

I have found this solution to be highly stable. 

The scalability of the solution is awesome. 

The deployment of this solution is easy. 

On a scale of one to five, I would rate the ROI of this solution as a three.

On a scale of one to five, with one being expensive and five being competitive, I would rate this solution as a four.

I would rate this solution as a nine out of ten.

We’ve used the solution for deploying several applications. We use it for testing purposes. It’s used for testing web apps and developing some proof of concepts.

It's easy to deploy web apps through Common Line or Visual Studio Editor, which is useful as I can deploy container solutions.

It is scalable.

The solution overall is very good.

The implementation process is easy. It’s also fast.

It’s stable.

There are no issues with the solution. I’m happy with the product.

We’ve been using the solution for three years.

It's a stable solution if you select the standard sizing. There are no bugs or glitches. It doesn’t crash or freeze.

The solution can scale well.

Technical support is rapid and extremely helpful. Whenever I have questions, they provide feedback very fast.

The product is straightforward to set up and quick to deploy.

I’m using the free version of the solution. I do not pay for licensing.

I’m using the latest version of the solution. I’m an end-user of the product.

I’d recommend this solution. You can start to use App Service immediately. You only need to have a subscription. If you would like to test App Service, then you only need to deploy in a free sizing version, and you can get going.

I’d rate the solution ten out of ten.

Our primary use case of the solution is for ETL. We're slowly moving everything over to Azure, so I think this will be our expected hub for the near future. I'm the chief analytics officer and we are a Microsoft partner.

The Azure data factory is the tool we're using the most. And again, we're using it for moving data around and data management. For now, we're pretty happy with the product although we're probably using it in a slightly more limited way. All the tasks we've done would have some reasonable degree of complexity and we've been able to achieve those tasks, or complete those processes. We're still getting familiar with it. 

There has been some building of pipelines where we've had to test and redesign a little so if there were maybe some easier to setup guides or more template data flows that would be an improvement. It would simplify the center processes. It would probably be impossible to have a template for everyone, but maybe there's some way to kind of simplify the initial stack and point frame for new users like ourselves, to make getting off the ground a little bit easier.

I've been using the solution for almost a year. 

The solution is stable. We don't have very large data volumes and we haven't yet migrated high data processing power onto the cloud. 

We haven't been attempting to push the boundaries in scalability. It's probably something we will gradually get to, maybe over the next six to 12 months where we will be migrating some additional processes and workload onto the cloud that we may start to see if scalability becomes an issue.

We haven't yet needed to contact technical support. 

The initial setup was reasonably straightforward. We've kind of been taking slow steps and migrating requirements as we gradually move certain tasks or certain processes into the cloud. We've done all the deployment ourselves. 

I think at the moment we're spending less than USD $100 a month. Because we're a Microsoft partner, we get a certain amount of credit on our partner account, but I don't think we've spent more than about $100, maybe $200 in a single month.

I would recommend the product. I would suggest giving yourself time to learn and adapt to the product. A lot of people would probably come to it having some historic or some existing software product in place and they're maybe migrating onto it. And so it will likely involve changing or redesigning how some existing process works. It's a good time to kind of learn some of the intricacies or the way Azure operates that might be slightly different to what they do on-premise. Ultimately it seems like it can do anything that you might be doing with a different tool or in a different location. It's just a matter of figuring out the configurations and the process.

I would rate this solution an eight out of 10. 

The primary use case has been pretty vague so far. Right now, my scope is on DevOps. I'm looking at it from the point of view of having a DevOps platform. We already have a team foundation server and are working from the cloud.

For me, the DDT has been very valuable. 

The code is very good. We are using that. We are currently exploring Azure Codes and Artifacts.

Overall, all of the features are very good.

It's a Microsoft solution, so it's very familiar in look and feel.

It's too early to really say what features are lacking at this point.

I am new to the intervention and I find it difficult to find my way around the user interface. I have my own learning tool. However, it could be simpler for new users.

The pricing could be a bit less.

We haven't been using the solution for too long.

So far, the solution's stability is very good. We have no complaints.

We haven't found any issues with scalability so far. It's been quite good.

We haven't requested any troubleshooting or help so far, as we haven't used the solution for too long just yet.

The deployment varies, but could take up to one or two months. There are a few things we are currently trying. We were looking for a CATD type of model.

We have our own team that is able to maintain the solution.

We've had a long business relationship with Microsoft. We're partners.

We're still in the process of exploring the solution. However, so far, I would recommend it. I'd rate it eight out of ten.

The Data Factory is very good, as is the SSIS, which I also use on the cloud.

The cost of the solution needs improvement.

I've been using the solution for three months.

We're still testing the product. We occasionally have some problems and get some errors. Right now, we have a lot of issues with it.

The product is scalable.

The solution is quite expensive. If you need more features, you need to pay for them.

We use the cloud deployment model.

I'd rate the solution seven out of ten. There are other solutions that seem to be okay as well. Windows, for example, has a good protocol. There's also AWS, but it's just on the cloud.

Azure App Service is a fully managed Platform as a Service (PaaS) that integrates bunch of services into a single service. One of its valuable service is Azure Web Apps that helps to develop and deploy enterprise-ready web applications. Microsoft Azure will take care of application deployment and management, while the developer only needs to concentrate on app development.

It is not unsual that we run into problems related to the deployment and post-installation. But Azure team is aware of these issues and continuously keeps improving the Azure stack.

The solution is very stable.

Microsoft provides a lot of scalability in all their services. Microsoft provides services and infrastructure, but for full scalability, the maker should take into consideration the scalability of the app home. The full scalability Microsoft provides is a way to scale up and scale up in your environment. But it doesn't take responsibility to make your web application scalable or not. It helps you to scale up, but it doesn't take care of your application's scalability.

Technical support from Microsoft is very good at all levels.

The initial setup is not too simple but not too complex. The interface makes it easy to use if you have known it for a while. For me, it's easy because I've already gotten used to it. But it could be, complex if you haven't.

The initial setup level of difficulty is dependent on what you want exactly. To set up a website on the app service, for example, is very easy for a simple website because all you need is to develop your website, build it with the Visual Studio, and configure. Once you want to deploy to app service, once you finish, it's only one button you click and everything will be deployed. It's very easy.

Deployment depends on how big your website is, so I cannot say exactly how long it will take in every case, but it is quite fast. It depends what are you sending, how many megabytes you're sending to the app service, but the app service is very fast. If you have a small website, just a few megabytes, 2, 3, 4, megabytes, you will see that it is very fast, but if you have a website with a lot of updates that takes probably five minutes, or ten minutes. That's because you need to push data to push the files to app service. The thing that I can tell you about the in-app service is that because the in-app service normally uses clocks, that means you have a development environment, staging and production environment, the customer can push more into the development environment or staging and then swap. And to swap is quite fast as well. That's the only bottleneck that is possible but Microsoft guarantees no downtime.

Most of the time we configure the ICG configuration and we put the effort in at the beginning to set up the pipeline and want to set it up so that it works automatically, so if you want to start a push code or anything will be deployed automatically. That way, fewer people are required down the road.

The benefits and costs of the Azure App Service plan varies between different tiers of web apps. It is free if you choose the Free and Shared plans app service. These plans are good only for development and testing purposes. So, before you start setting up your app service plans with multiple apps, make sure you are aware of how your chosen plan implements this.

Azure App Service is too easy to setup and appropriate for developers with no knowledge in infrastructure.

I would rate this solution an eight out of 10.