Microsoft Azure App Service Reviews

Microsoft Azure App Service is an easy way to host applications and web applications. If you have a container as an application, or if you have .NET technology, Python, PHP, and other languages and stacks, you can use Microsoft Azure App Service to host them. It is very straightforward to automate the deploying and configure. It is very easy and useful.

Currently, the Microsoft tools I have more experience with involve using Azure cloud and Azure DevOps.

The best features are how easy it is to use and host web applications.

We use Microsoft Azure App Service extensively here.

I utilize the continuous integration feature, integrated with Azure DevOps. We use the CI/CD inside Azure DevOps and Azure DevOps deploys the applications in Microsoft Azure App Service.

When using a Linux App Service or containerized App Services, the logging is not as good as when using the Windows version. The Linux App Service should be more user-friendly, focusing on logging, troubleshooting, and similar features.

With Microsoft Azure App Service, it is more difficult with Linux or other container solutions because there are many options. When creating an App Service, you can create it as Linux or Windows. After that, you can choose some stack or use Docker to container. When using Linux with container, the logging functionality is not as robust.

I have had experience with Microsoft Azure App Service for at least five years.

We used the built-in authentication and authorization features only once. It is an interesting and good feature, but it is not correlated with our use cases here.

In production environments with Microsoft Azure App Service, there is a feature called Diagnose and solve problems. Inside this feature, there are many tools to see how your application is performing. It can detect issues such as memory leaks, excessive CPU usage, or connectivity issues. This feature allows us to pinpoint very quickly what is happening when an application is not working correctly.

It is easy to calculate and know how much you are going to spend.

When evaluating their service or technical support with Microsoft Azure App Service, it has been pretty good. We rarely have issues here. The times that we needed support, it was adequate. While contacting support is not always a pleasant experience, they attended to our needs satisfactorily.

The initial setup of Microsoft Azure App Service is easy, but I have been using it for many years, so I might not be the best person to provide an objective assessment.

You can start with a basic plan, which costs very little. As your necessity and workload increase, you can scale up and add many nodes. If you need to host three, four, or five nodes with high availability, everything is included in the price. If you do not need high availability, you do not pay for it, but if you want it, the prices are very straightforward.

I still have experience with Microsoft products in general. We are focused on Azure only. We are customers of Microsoft. My role is a solution architect, and I do not deal very much with infrastructure products. I do not deal with other Microsoft tools such as Intune or Purview. We do not use Configuration Manager, such as SCCM or CSM.

On a scale of 1-10, I rate Microsoft Azure App Service a 9 out of 10.

The typical use case for Microsoft Azure App Service is for our clients to utilize scalability and security. The clients are using the Microsoft Azure services for security reasons and highly scalable and reliable infrastructure. Most of the clients are using Azure services, as we developed our applications and host them on Azure for seamless operations.

The best features of Microsoft include Office 365, collaboration suites, MS Teams, and SharePoint. We are using SharePoint for collaboration across the entire organization and to share documentation with our clients. We are also using infrastructure through Microsoft Azure, so our own websites are hosted on the Cloud, including Web Application Firewall, Azure clusters, and Kubernetes.

The best features of Microsoft Azure App Service are its capacity for scalability, security, and basic support functionalities.

Microsoft Azure App Service's automatic scaling and load balancing features are inbuilt capabilities within the application. There are two types of applications: Kubernetes for load balancing and the virtual scale set. We are using load in certain applications that automatically scale; these features are present in Azure, and at the front end, we are using load balancers.

Regarding the built-in security features, such as authentication and SSL certificates, each web request passes through the Web Application Firewall and the SSH, SSL certificate, and Secure Socket Layer certificate. Each authentication integrates with Microsoft Identity Access Management, as we create users on Azure Active Directory Azure ID to use for the applications.

Microsoft Azure App Service could be improved in various application functions, as we have a need for improvement after monitoring and diagnosing each application. We will redefine our logic, and our development and infrastructure teams will discuss and improve the performance of requests and address time-consuming processes.

I have approximately 7 to 8 years of experience working with Microsoft Azure App Service.

The initial setup of Microsoft Azure App Service is straightforward, and for two or three clients, we have configured more complex setups. App Service depends on the requirement as we have multiple clients. We initially started with virtual machine services, then graduated to App Services and database services. Now we are using Kubernetes services for scalable and high-demanding production requirements based on client needs.

My experience with pricing, setup costs, and licensing of Microsoft Azure App Service is based on 7 to 8 years of dedicated work with Azure and its services. Before that, we provided Active Directory and server infrastructure through perpetual licensing solutions to our clients.

The price of Microsoft Azure is comparable to Microsoft AWS and Google. Sometimes, the cost for the Indian market seems a bit on the higher side, but we help customers optimize their solutions. We provide solutions at the optimum minimum cost from start to peak load; the cost is not excessively high but is at a medium level for these solutions.

I have experience with Azure services such as App Service, VM, virtualization, Web Application Firewall, load balancing, and traffic managers.

The integration capabilities are strong as we mostly integrate REST API with other solutions. We are using REST API to integrate with various solutions to get and post data from third-party applications. Additionally, we use file-based solution stores, along with FTP or secure FTP for file-based solutions, but mostly we are using REST API.

On a scale of 1-10, I rate Microsoft Azure App Service a 9.

I use Microsoft Azure App Service within my industry primarily for web app deployments. However, I don't use it extensively since I currently operate on an intranet system.

My organization has significantly improved operations using Azure App Service. Before integrating Azure, many applications were not cloud-based, leading to version control issues. Now, with everything integrated, these problems have been solved, thanks to Microsoft's good work.

The most valuable feature I find in Azure App Service is Microsoft Teams, as it is embedded within Office 365 and integrated with SharePoint. This integration is heavily utilized within Microsoft Teams and has proved crucial for my operations. 

The integration capabilities of Microsoft Azure App Service have greatly enhanced my ability to handle global web operations and support various functions, which were previously challenging without such integration.

I would like to see enhancements in the AI functions, specifically in the AI co-pilot within Azure. I deal with numerous business demands and case studies that need implementation.

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

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

I rate the scalability of Microsoft Azure App Service as eight out of ten.

Customer service is very helpful. Microsoft provides support for a lot of add-on or customized integration requests.

Negative

Prior to using Azure, many applications were not integrated in the cloud, which caused version control issues.

Setting up Azure App Service took approximately five days for installation, primarily due to the data migration required from SAP.

My implementation included a large team of about twenty people from various sectors such as engineering, consulting, and security. I have global sites, including those in Shanghai and Mexico, which were also involved in the project.

It is an expensive product, primarily due to the licensing fees.

I utilize SharePoint as a default for my internal processes.

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

I appreciate how well it integrates applications into the cloud, solving significant version control issues.

I use Microsoft Azure App Service to create some applications personally, but not so much. I use the tool to try to learn a new language or upgrade to any new framework. I use similar tools to manage application components, but I don't do it so much.

A few weeks ago, I was trying to use a new web application with Microsoft Azure App Service. I thought it would be better to have a template to publish directly to Microsoft Azure App Service using GitHub because there were some documents related to Azure DevOps. If you use GitHub Actions, I would say that it is a little bit more complicated.

I have been using Microsoft Azure App Service for years. I am a developer.

I don't remember facing any stability issues with the product.

The scalability of the product is enough in my case. Even though I was working with a company that was using Azure, the company had an application with 1,000 to 2,000 users, meaning there were a lot of users per day. The scalability part of the Microsoft Azure App Service was enough for all of the users.

I haven't had a chance to raise a lot of tickets with the support team. I will only raise requests when it is critical. If I used to create a ticket for support, I have seen that the services were very fast and someone from the technical team would always contact me to try to provide me with a solution. I rate the technical support an eight out of ten.

Positive

The product's initial setup phase is fast, and creating a new component and starting is easy.

The solution is deployed on a public cloud.

I can create a new app service and configure it quickly if everything is okay in three to four hours, but it all depends on the application. If the application is small and I know about the language and the framework, the tool is fast. If the application or its architecture is complex, you can deploy the tool daily or weekly. It all depends on the application.

The product is not expensive. The tool's price is okay for all of the benefits you get from the solution. Compared to using AWS or Google Cloud, Azure is faster.

I use Microsoft Azure App Service in my web development workflow since I use it for some web applications that are similar to maybe some startup applications. I think using or connecting Microsoft Azure App Service with GitHub and Azure DevOps is really fast. I prefer using Azure because it is fast and allows continuous integrations. Considering my perception, using Microsoft Azure App Service is really fast.

The product has proven to be beneficial in managing web apps in general, especially considering that with the tool's free account, it is really great to use it for tests, maybe create a small application, or try to learn different things.

When it comes to load balancing capabilities, I would say that I remember using Azure Traffic Manager when I was working in my company a few years ago. The configuration part was complex. We had to do the configurations with all the complexities for which we had to personally specialize in it, but after doing so, it started working fine.

I recommend the product to those who plan to use it.

I rate the tool an eight out of ten.

I use the solution in my company for the applications we have on the on-premises part, and we want to convert them to SaaS or PaaS. We want to use Azure Kubernetes Service (AKS) with the solution, as there are areas that depend on both tools when we want to migrate something to the cloud.

The tool's most valuable feature is that we don't have to worry about the infrastructure. The cost or price of Azure is lower than that of the on-premises version, which is why we might want to implement our solutions in Azure.

Azure has too many tools that can make your work easier. With Azure, when we are going to implement a chatbot with translation for text-to-speech, we found that it should already have a tool that does that. In our company, we have to have our budget to add more tools, and then the developer solves the issues associated with the product. Too many tools in the product can be beneficial.

The tool's UI is an area of concern that needs improvements. I don't like the UI so much, so it is a problem. I don't like the tool's UI or how it looks, but it is easy to use. The UI is so clear on how to start with them. If you take a course or a tutorial associated with the tool, the UI becomes easier.

I have been using Microsoft Azure App Service for a year.

Stability-wise, I rate the solution a nine out of ten.

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

I rate the technical support an eight out of ten.

Positive

On a scale of one to ten, if ten means easy, I rate the product's initial setup phase as a nine.

The time required to deploy the product depends on the volume of the solution we plan to use. In the media space, the deployment takes a week, but it is easy to manage it.

The solution is deployed on an on-premises model, but we are using it more in the cloud infrastructure.

In our company, we have a deployment area with people in the infrastructure team, where around 20 people work. These people don't work on just one deployment. Three engineers are involved in the deployment of the solution, or sometimes, only I am involved with the solution.

The tool is easy to implement and learn.
 

The product's price is low, especially if we compare it with other tools or clouds, like Google Cloud or AWS Cloud. Sometimes, Azure is cheaper than the other clouds.

We don't have a team just for the tool's maintenance. It is maintained by the same developers who develop the solution. We have teams with five or six developers. In exact cases, the people who do the maintenance are the architects or me.

The tool's integration features are easier to manage if you use Microsoft technologies. Apart from Microsoft, if you use other technology, programming language, or another framework, the tool can be easily integrated. The integration is easy if you use Kubernetes or Docker with DevOps. The tool's integration features are very simple and easy to use.

I rate the tool a nine out of ten.

The main use cases for Microsoft Azure App Service are mostly related to creating front-end applications, which would connect with a document bot we were developing.

Regarding its automatic scaling and load balancing features, those capabilities are really effective. Certain philosophies are inspired from Kubernetes as well, which makes these features essential and beneficial.

In terms of handling traffic spikes and maintaining optimal performance, it has been highly effective.

I have used its integration capabilities with Azure Functions and Azure databases, specifically Redis, and the integration process was straightforward.

I am familiar with its built-in security features such as authentication and SSL certificates. We use NVA and have integrated it with most of our in-house applications. We are also planning to use NVA for our product where we are trying to offer our product as a PaaS offering.

I evaluate the effectiveness of Microsoft Azure App Service's monitoring tools and diagnostic capabilities as good. Though as an architect, I wouldn't recommend any kind of vendor lock-in, if you are comfortable with the budget, Azure Insight is beneficial as it comes with all monitoring capabilities out of the box.

Microsoft Azure App Service could be improved if it had AI-based integration, which would be much more beneficial. Currently, there's a trend toward prompt-based deployment where one can create a pipeline based on simple English prompts. The system should handle all the setup, allowing users to review and complete the deployment. This kind of integration is available in GCP, but I'm unsure about its availability in Azure, though it should be there.

The price is an issue relevant only for Azure Firewall because until we figured out the policies, there were issues. Once we determined the required policies, we were able to budget the pricing and set up alerts on the pricing part.

For Microsoft Azure App Service, we did not have the same pricing issues. App Service is straightforward, and most of our usage was related to smaller applications, primarily POCs. We didn't encounter pricing issues because we had the option to start the application. For production-based applications, fine-tuning might be necessary, and pricing-related conflicts might arise.

We have not used the hybrid and multi-cloud capabilities of Microsoft Azure App Service to deploy applications across different environments.

Overall, Microsoft Azure App Service is a very effective tool. On a scale of 1-10, I rate this solution a 10.

I work with Microsoft Azure App Service Functions and Static Web Apps. I am searching for new applications and have been doing so for three or four months, approximately.

For purposes of using Microsoft Azure App Service, we have made an HTML page that performs various tasks, for instance, or a service bus for messaging to other applications.

Regarding the best advantages of Microsoft Azure App Service, we are still exploring, so we cannot determine what's most or least valuable as it's new for us.

Regarding functionalities or capabilities that I am using most frequently, I question what features are meant, whether it refers to applications.

I find Microsoft Azure App Service has some disadvantages. It can become easily complex. There are so many possibilities that it's difficult to know what's the best approach, and we can make it too complicated for what it's meant to be.

The main problem is that it's overwhelming. Finding the best practices and the optimal way to implement something is always challenging.

They should improve the learning curve, enhance documentation, and focus on best practices.

I have been using Microsoft Azure App Service for just a few months. It's very new to us.

Finding the best practices and optimal way for deployment is always challenging. The deployment process can be complex, and there is a significant learning curve, making it difficult to understand in the beginning.

I find it stable; there are no problems.

I don't see limitations; it is also scalable.

I have dealt with technical support from Microsoft one time. It was a good experience.

Positive

I find that Microsoft Azure App Service can be complex to set up and to deploy.

I am not currently using the multi-cloud capabilities or load balancing features.

I have tried to integrate Microsoft Azure App Service with some functions such as Azure SQL database and other Microsoft services. The integration works smoothly once you understand the process.

My usage is currently very limited. There is always room for improvement, which is why I cannot give it a perfect score.

I am now experimenting with Azure Functions, and I find that it's not very easy.

My rating for Microsoft Azure App Service is 8 out of 10.

We primarily use web app services and Kubernetes. I mostly use Microsoft Azure App Service for bespoke applications hosted on web services.

The most valuable features in the context of development and deployment are the integration with SDKs and the infrastructure standpoint. I primarily use horizontal auto-scaling rather than vertical scaling.

The main area that requires improvement is the function apps and logic apps, specifically from a VNet integration standpoint. When running in private network configurations, Logic Apps do not fulfill most of the requirements. Deploying Logic Apps in a private network environment becomes complicated due to the extensive white testing and configurations needed at the networking layer.

I have been working with Microsoft Azure App Service for a long time.

I find Microsoft Azure App Service to be quite stable, and I would probably rate it at eight on a scale of ten.

Expansion in terms of SKU configurations can be convoluted and depends on individual use cases.

I have found that technical support from Microsoft is generally good. The quality of support depends on the region where the support ticket lands, with regions like Europe, the US, Canada, and India providing very good and immediate support.

Positive

The initial setup for Microsoft Azure App Service is simple. It is very easy, quite understandable, and very easy to follow through.

The pricing for Microsoft Azure App Service is reasonable, and I would describe it as normal.

I have not seen any major competition to Microsoft Azure App Service in the market so far.

Overall, I would rate Microsoft Azure App Service as nine out of ten.

I primarily use Microsoft Azure App Service to deploy Python-based applications. It was majorly used for deployment purposes only. When you buy a virtual machine, you need to do lots of configuration, but using Azure App Services gives you lots of flexibility. It's easy - you just upload the code and do a few clicks.

Deployment is really quick, which eliminates the need for a separate team dedicated solely to deployment. A simple software engineer can handle it, making live updates seamless and reducing the need for thinking cycles.

The ability to deploy applications directly from my Visual Studio Code without needing to access Azure is helpful. Additionally, scalability is straightforward, and you can quickly adjust the resources to meet demand.

The interface is a bit complicated and not straightforward. Documentation is not well-organized, making it difficult to find current and relevant information. 

The logging process using stream is not always accurate, and the pricing is quite high, often twice the price of virtual machines. 

Additionally, in terms of scalability, they do not offer the option to have two different virtual machines with separate configurations.

I have been using Microsoft Azure App Service for more than a year now.

I have never faced any stability issues in my last year of usage, so I would rate its stability nine out of ten.

Scalability is easy and helps improve application performance. However, there is no option to configure different virtual machines with various configurations, like one with eight GB of RAM and another with 16 GB.

I have had poor experiences with customer service. Although I have rarely required support, whenever I created a ticket, I never received an answer. I would rate their support one or two out of ten.

Negative

I used Amazon AWS virtual machines before. However, Azure App Service is much better, although it's costly.

The setup is quick and easy, taking a maximum of five minutes if you know which resources to choose.

The pricing is very high. It's approximately twice the cost of AWS virtual machines. While the deployment feature is convenient, the costs make it unaffordable for many in the industry.

I recommend Microsoft Azure App Service because it is easy to deploy. However, the pricing could be a deterrent for many users who might prefer manual configurations at a cheaper rate.

I'd rate the solution seven out of ten.

We have been using Microsoft Azure App Service to host small apps. We have either hosted applications on VM directly or we use Microsoft Azure App Service to host our applications. We have various applications for sales, service, and other purposes where we're using Microsoft Azure App Service.

Within one Microsoft Azure App Service, we can have multiple applications hosted. We thought that it would help save costs instead of using VM, as we can use Microsoft Azure App Service to host multiple applications.

We use Microsoft Azure App Services extensively. It is easy to integrate with other services through simple drag and click functionality.

We have been successfully integrating it with SQL databases and Azure Functions.

Auto-scaling is helpful for Microsoft Azure App Service. However, recently, we are seeing that Microsoft Azure App Service is consuming a lot of resources. We plan to evaluate whether we should switch to containers or use AKS instead.

For Microsoft Azure App Service, they need to make it less resource-intensive or less costly, because from a cost perspective, we are seeing that it is proving more expensive for us.

We have been working with Microsoft Azure App Service for two to three years.

The scaling ability for Microsoft Azure App Service is satisfactory, warranting an eight out of ten rating. However, if we were to switch to containers, that would be better as we could scale much faster and easier.

Support for Microsoft Azure App Service varies in quality. Because we have premium support, we get responses quickly. However, many times we have observed that they send someone who cannot solve the issue immediately and takes some time. An expert typically arrives after three or four hours to work on the problem. On a scale for support, this warrants a six or seven out of ten.

The setup process for Microsoft Azure App Services is simple.

I have not tried other products, but I think Google or AWS would have good competitors for Microsoft Azure App Service.

We have been integrating Microsoft Azure App Service with SQL databases and Azure Functions. Based on our experience, we rate Microsoft Azure App Service a 7 out of 10.