Microsoft Azure App Service OverviewUNIXBusinessApplication

Microsoft Azure App Service is the #4 ranked solution in top Mobile Development Platforms and #9 ranked solution in top Rapid Application Development Software. PeerSpot users give Microsoft Azure App Service an average rating of 8.6 out of 10. Microsoft Azure App Service is most commonly compared to Microsoft Power Apps: Microsoft Azure App Service vs Microsoft Power Apps. Microsoft Azure App Service is popular among the large enterprise segment, accounting for 70% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 17% of all views.
Microsoft Azure App Service Buyer's Guide

Download the Microsoft Azure App Service Buyer's Guide including reviews and more. Updated: November 2022

What is Microsoft Azure App Service?

Microsoft Azure App Service is an HTTP-based mobile application development platform and solution. It is designed to enable organizations to completely control their application development and hosting processes.

Microsoft Azure App Service Benefits

Some of the benefits that come from using Microsoft Azure App Service include:

  • A high level of security. Microsoft Azure App Service comes with enterprise-level and industry-standard SLAs through the use of PCI security standards. Users can go about developing their applications without having to worry about exposure to security risks. Microsoft Azure App Service keeps the application development process secure so that all that users have to worry about is creating their application.
  • Collaborate and develop applications from anywhere. Teams that are spread out across the globe can collaborate and build applications from anywhere that they happen to be. Microsoft’s global data center is a cloud hub that developers can take advantage of to connect their teams if they are located in disparate locations. It can handle all of a developer's application hosting needs.
  • Multi-format and multi-lingual support. Microsoft Azure App Service supports both physical machine and virtual machine formats. In addition, it also supports a variety of different programming languages.
  • Utilize pre-fabricated templates. Microsoft Azure App Service gives developers access to an extensive list of templates. These can both ease the process of planning the development of applications by providing developers with ideas and make it easier for the developers to build them.

Microsoft Azure App Service Features

Some of the many useful features Microsoft Azure App Service has to offer include:

When users choose to employ the Microsoft Azure App Service solution, they gain access to many different capabilities. These features include:

  • Manual or automatic auto-scaling capabilities. Microsoft Azure App Service enables developers to control how their applications auto-scale. Developers can employ the auto-scaling feature by hand or set it so that it automatically rescales according to their needs.
  • IDE integrations. Microsoft Azure App Service can easily integrate with various IDE software solutions. This gives developers access to many analytic, debugging, and monitoring options.
  • Deployment slots. These are virtual spaces where developers can test and deploy new versions of their applications while working on them. This feature allows developers to resolve any issues before the new version of the application is put into production.

Reviews from Real Users

Microsoft Azure App Service’s versatility offers organizations that use it a great deal. It is a very complete, ready-to-use, out-of-the-box mobile development solution that gives users the capabilities that they need to design their mobile applications with the greatest level of ease. In addition, users can employ the cloud to scale operations so that their applications have the proper amount of space to run at the time that they need it.

Andriy L., the Azure practice leader at a computer software company, writes, “I like that it's a ready-to-use, out-of-the-box solution that provides all of the necessary functions for customers, such as codes that can be quickly switched from the production version, or test and DEV versions to production.”

Yasir M., a solution architect at Komatsu, writes, "The best feature is scalability, which allows you to target potential clients worldwide by connecting the application to a local server. This makes the application readily accessible, and the response time will be much better."

Microsoft Azure App Service was previously known as Azure App Service, MS Azure App Service.

Microsoft Azure App Service Customers

Real Madrid, Absolut, AccuWeather, Heineken, NBC News, Paramount

Microsoft Azure App Service Video

Microsoft Azure App Service Pricing Advice

What users are saying about Microsoft Azure App Service pricing:
  • "Where there are different customer sizes, some customers consume $5,000 US dollars per month. I have some customers who pay and consume more than $20,000 US dollars per month, for example. It is determined by customer sizes and requirements, which vary from month to month."
  • "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."
  • "The cost depends on the App Service plan that you choose. There are a number of tiers available."
  • "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."
  • Microsoft Azure App Service Reviews

    Filter by:
    Filter Reviews
    Industry
    Loading...
    Filter Unavailable
    Company Size
    Loading...
    Filter Unavailable
    Job Level
    Loading...
    Filter Unavailable
    Rating
    Loading...
    Filter Unavailable
    Considered
    Loading...
    Filter Unavailable
    Order by:
    Loading...
    • Date
    • Highest Rating
    • Lowest Rating
    • Review Length
    Search:
    Showingreviews based on the current filters. Reset all filters
    Andriy Lyubimov - PeerSpot reviewer
    Azure Practice Leader at a computer software company with 5,001-10,000 employees
    MSP
    Top 10
    Good backup and restore, with vertical, horizontal, and DEV scaling options
    Pros and Cons
    • "I like that it's a ready-to-use, out-of-the-box solution that provides all of the necessary functions for customers, such as codes that can be quickly switched from the production version, or from test and DEV versions to production."
    • "It would be fantastic if Microsoft morphed after my exit service, removing it from subscriptions and moving it to different regions, especially for that service."

    What is our primary use case?

    We mostly use Microsoft Azure App Service for websites, such as content management systems, WordPress, and others, which are built on Azure Web Repair and App Services.

    What is most valuable?

    I like that it's a ready-to-use, out-of-the-box solution that provides all of the necessary functions for customers, such as codes that can be quickly switched from the production version, or from test and DEV versions to production. 

    Quote backup and restore vertical and horizontal scaling, and DEV scaling are all available. In this case, developers do not need to learn and spend their time on the configuration for the platform, just coding and asking to compute, which they need and that configuration, which platform provides them.

    What needs improvement?

    Price could be reduced.

    Particularly with Azure Web Apps. According to their current architecture, moving services from one Azure subscription to another is difficult.

    Customers can consume the Azure platform through a variety of subscriptions from various partners, financial visions, current political visions, and so on. Some services on the Microsoft Azure platform can be moved automatically from one subscription to another based on security and financial rules, while others cannot.

    Azure Web Apps are the type of service that does not automatically move from subscription to subscription, and region to region. A lot of manual labor must be performed by their organization, customer, and engineers, if necessary.

    They must pay too much attention to how to plan this, how to switch off, switch on, on which days, at what times, and so on. A lot of administrative work is done, but it's not very good. 

    It would be fantastic if Microsoft morphed after my exit service, removing it from subscriptions and moving it to different regions, especially for that service.

    For how long have I used the solution?

    I have used Microsoft Azure App Service for the last 12 months.

    Because it is cloud-based, there is only one version.

    Buyer's Guide
    Microsoft Azure App Service
    November 2022
    Learn what your peers think about Microsoft Azure App Service. Get advice and tips from experienced pros sharing their opinions. Updated: November 2022.
    653,522 professionals have used our research since 2012.

    What do I think about the stability of the solution?

    Microsoft Azure App Service is stable. It's good enough. it's present here, but anyone can take it if it's needed. Especially now, Microsoft offers a very special support program in Ukraine. For example, if a customer needs to support their business processes, they can use any Azure solution for free until the end of the calendar year.

    What do I think about the scalability of the solution?

    Microsoft Azure App Service is a scalable solution.

    How are customer service and support?

    We are a technical support team, and we handle all of our support needs. We have not contacted technical support.

    I am Microsoft-certified trained. This is why I don't require any additional support assistance; I train others. In other words, every Microsoft commercial partner receives direct Microsoft support. For example, Amazon provides additional information from the traditional partner channel, or by extra support, through premier support contracts. All of them must be present on a commercial basis in order to provide truly high-quality services to customers.

    Which solution did I use previously and why did I switch?

    I am a technical architect and I have some commercial partners. I work as a system integrator. It is a software, global company that specializes in delivering cloud software, solutions, and services. As for this, I have over 25 years of experience with all stacks, including Azure, AWS, Google GCP, Oracle Cloud, and others. I was very interested in the Zimbra and Microsoft Exchange compilation because, in my opinion, based on my experience and statistics, Zimbra is not widely used in our accounting and based installation. However, one commercial customer inquired about my thoughts on Zimbra in conjunction with Exchange. It was very unfamiliar to me, which is why I attempted to conduct independent research on Zimbra solutions. Who and how are relevant to that question. I don't think we'll implement Zimbra because it's outside of our stack, but it was very interesting to get some perspective on the questions, nothing special, just vision and experience and growth.

    We use what our customers requested from the Microsoft stacks, which are mostly infrastructure as a service solutions. It is a very limited number of PaaS installations or implementations, such as Aurora or Microsoft SQL, Azure SQL as a service, web applications on Azure, and so on. Of course, SaaS, such as Office 365, is a good option, but I can't say what other options aren't because the Microsoft stack is our primary commercial platform for our sources. It's fantastic; it provides us with some commercial advantages.

    We recently used Azure, virtual machines, virtual networks, and virtual storage, as well as Azure IaaS Stack, Azure Virtual Machines, and Azure Storage.

    Because Azure Web Services is based on the Azure IaaS Stack, it is infrastructure as a service. It's a platform as a service that's based on IaaS for some purposes, but our customers don't need the services to bring ready-to-use apps because they don't have a lot of education and institutes. Overall, Qualys solutions are not widely used in Ukraine, for example, by schools, governments, and institutes, due to commercial issues and, in particular, our notice time.

    We chose Microsoft Azure App Service because the customer inquired. We are a very commercial company, and if the market or the customer did not request it, we did not provide it. If the customer requests it, we will provide it.

    How was the initial setup?

    I don't recall any problems with the initial setup at the time because I believe it was adequate. I didn't hear anything about widespread or public knowledge of some issues in that area.

    What was our ROI?

    Most importantly, not too much. The customer has a high level of financial maturity to value DPI; they do not discuss ROI or other metrics. They simply book on current, can say spending, if current model spending is adequate.

    What's my experience with pricing, setup cost, and licensing?

    Price could always be cheaper.

    It is not about the license fees, but rather about the pay-as-you-go services.

    Customers consume varying amounts of quality services and pay roughly the same amount. Where there are different customer sizes, some customers consume $5,000 US dollars per month. I have some customers who pay and consume more than $20,000 US dollars per month, for example. It is determined by customer sizes and requirements, which vary from month to month.

    What other advice do I have?

    I would advise paying closer attention to the architecture of the solutions. If the architecture is well designed, this will be a very good placement on cloud solutions; otherwise, it will be placed incorrectly. It's a common situation, and owing too much money as it should be.

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

    We are a Microsoft partner.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Microsoft Azure
    Disclosure: My company has a business relationship with this vendor other than being a customer: partner
    Flag as inappropriate
    PeerSpot user
    Babatunde Ojo - PeerSpot reviewer
    Cloud Engineer at Tek Experts
    Real User
    Can run a function faster and more frequently, is easy to utilize, and only requires minimal setup
    Pros and Cons
    • "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."

    What is our primary use case?

    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.

    What is most valuable?

    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.

    What needs improvement?

    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.

    For how long have I used the solution?

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

    What do I think about the stability of the solution?

    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.

    What do I think about the scalability of the solution?

    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.

    How was the initial setup?

    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.

    What's my experience with pricing, setup cost, and licensing?

    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.

    What other advice do I have?

    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.

    Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
    Flag as inappropriate
    PeerSpot user
    Buyer's Guide
    Microsoft Azure App Service
    November 2022
    Learn what your peers think about Microsoft Azure App Service. Get advice and tips from experienced pros sharing their opinions. Updated: November 2022.
    653,522 professionals have used our research since 2012.
    Technical Lead at a tech services company with 1,001-5,000 employees
    Real User
    Top 10Leaderboard
    A multi-tenant environment where customers can load and run applications
    Pros and Cons
    • "The most valuable feature is the ability to scale the application."
    • "The outbound connectivity is not great."

    What is our primary use case?

    Our primary use case for this solution is hosting web applications which can be Linux or Windows-based. Microsoft Azure App Service is a multi-tenant environment where customers can load and run the application. It is similar to a platform as a service.

    What is most valuable?

    The most valuable feature is the ability to scale the application. It scales dynamically and comes with two features. If you can find a fabulous feature in the Azure Functions app, it allows you to scale, so you don't need to worry about manually scaling or setting any scaling parameters. Then it automatically does the scaling on its own.

    The other feature comes with VNet integration. So we can connect the Microsoft Azure App Service to a VNet so that it can privately communicate with other resources within Azure with a private IP. It also comes with the CDN feature, which can automatically load in some of your configuration files and use it instead of going back to storage to pick that up. It also has awesome features like backup, so you don't need to set up a recovery service, as it automatically does that. So you can back up the existing state of your application in case of any loss. In a nutshell, it has dynamic tools.

    What needs improvement?

    The outbound connectivity is not great but can be improved because, on virtual machines, the Microsoft Azure App Service uses four or five outbound IPs. So basically, if you want to communicate with an external source, you can use outbound IPs. For example, you must whitelist the outbound IP when communicating with an SQL database externally. However, because it's a multi-tenant environment and other customer applications are being shared on a skills tab, there are always limitations in the smart port. So each customer has a particular allocated smart port, which they should exhaust. It helps to work with the code. Regardless of features like a firewall where they have a hub and an environment they have features like a front door which can increase the smart port's limits to about 64,000. Hence, it will be good to have one IP without needing to add any other infrastructure.

    Additionally, they can improve scaling the typical environment in terms of scalability. I believe the limit for the multi-tenant environment is about 20 to 30 maximum on the PV3. So if they can increase that, other than having these significant scaling limits for the Microsoft Azure App Service environment, which is about 200, that will also help.

    Also, dedicating one outbound IP for App Service will go a long way.

    For how long have I used the solution?

    We have been using this solution for approximately three years.

    What do I think about the stability of the solution?

    The solution is stable.

    What do I think about the scalability of the solution?

    The solution is scalable.

    How are customer service and support?

    They have a good support team. We don't think the front-end support is of concern because the front end has to talk to the internal respective application engineering team. Sometimes the core platform issues may take about two months or more. They can answer your queries, and they can help you do investigations.

    Additionally, depending on your support package, if you have a premium plan, you get the best because you have support engineers who are intelligent. But you get different services with the pro-direct support plan. There's miscommunication between the front end and the application engineering team. I think that's something that they need to improve. On a premium plan, you get excellent support. I rate support for pro-direct a six out of ten and premium support an eight out of ten.

    How would you rate customer service and support?

    Positive

    How was the initial setup?

    The initial setup is easy. You can set it up through the portal, a template, or Terraform. It integrates with other features like Docker so if you have your image in Docker Hub or ECR, you can select the image, and it pulls those images in and runs your application.

    It has many features, and other deployment methods like Bitbucket, FTP, DevOps, and GitLab can integrate these things into Microsoft Azure App Service. It is easy to set up because you don't need to start building servers. We also don't need to complete any maintenance. 

    What's my experience with pricing, setup cost, and licensing?

    The price of this solution is competitive. It works as an App Service plan so you can have multiple App Services that are part of a plan. So, for example, you can have about 10 App Services in an App Service plan. It's like a VM, where you have different applications running and you are not charged for all of the applications. However, you are being charged for the plan, so I think it's worth having that setup. At the same time, you need to plan how your costs will be and their ranges of variations. As we call it, SKU is where you can easily factor in so it is okay in terms of price.

    One of the best products is the Functions app, which comes with serverless computing in the sense that it gives you about a million transactions for free every month. That is one of the cheapest. So you don't need to worry about how long your function triggers, just that if it scales more than that and performs more transactions, you get charged for it. The exact cost depends on the SKUs.

    What other advice do I have?

    I rate the solution an eight out of ten. 

    Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
    Flag as inappropriate
    PeerSpot user
    Reema Nandi - PeerSpot reviewer
    Application Development Associate Manager at Accenture
    Real User
    A solution with great server management and helps improve performance.
    Pros and Cons
    • "We are able to do millions of things simultaneously."
    • "The configuration is slow without understanding the systematic process."

    What is our primary use case?

    We use this product for integration and use a bidirectional approach. Some cases are created in service now, which are pushed to Salesforce. When an item is created in Salesforce, it is also created in ServiceNow which exposes some risk APIs. Those risk APIs are Salesforce, snow and sales group, but it's not enough for our portal because they need some customization, so we do it ourselves with function apps deployed over Azure. The function apps are forced through API and ServiceNow and application performance integration systems. These function apps are consumed by those APIs.

    What is most valuable?

    We are able to do millions of things simultaneously. Additionally, Azure maintains and manages the server, which is very helpful because we don't have to. The microservice architecture is also very good. Performance wise it is the best thing I have ever found.

    What needs improvement?

    The product could be improved by including crude operations. Previously, we provided it in the same application. However, when the operation went down, other operations also went down. This was one of the risks we had to overcome with this solution to avoid other operations being affected when one operation went down. With this resolved, the performance will be seamless because data can be handled simultaneously.

    For how long have I used the solution?

    We have been using this solution for the last six months. Microsoft Azure App Service has multiple plans and subscriptions. It provides access to certain subscriptions and specific profiles, fewer consumption plans and subscription premium plans. So when we work on logic or function apps, they provide certain resource groups. We can discuss certain logic and function apps when we have access to resource groups.

    What do I think about the stability of the solution?

    The solution is stable. Everything is organized. Additionally, access is provided to their help centres in case you face difficulty. When we had issues, we contacted them, and they made a ticket and resolved it.

    What do I think about the scalability of the solution?

    The solution is scalable. Approximately 50 to 100 people in different roles use this product in our company. However, I am unaware of the total amount of people that could be added to this product.

    How are customer service and support?

    Unfortunately, I cannot comment on our experiences with customer service and support at this time.

    How was the initial setup?

    The initial setup was easy. However, understanding the configuration was important because everything was very systematic. The configuration is slow without understanding the systematic process.

    Deployment is fast, and it takes a few seconds to publish it. This often occurs in our application because we have to make changes, but not all of our staff are involved in deployment. We take 15 minutes from the client and 15 for testing, but it takes only two to three minutes to publish.

    What's my experience with pricing, setup cost, and licensing?

    There are several plans available for different licenses and costs. When using this product for the first time, it is essential to understand the type of scaling required, the kind of skills needed and the level of necessary tiers. For example, to keep services running for up to 24 hours, there is a charge, but if you want to have your app services running for 12 hours daily, there is a different charge. You can also purchase specific plans. In addition, there are different types of client packages. Therefore it is important to explore each package to find the one best suited for the task required. We suggest using this product, which is helpful because it improves performance and loading times.

    Which other solutions did I evaluate?

    We chose this product because it has several plans, including consumption plans. My company will not have to worry about maintaining server systems. Hence, we only have to perform a daily routine after deploying and maintaining the service. Our company handed these tasks to Azure. Microsoft Azure takes care of our content application, including when to turn it off. We pay for these services, which saves us the pain of managing them. This is very important when using Microsoft Azure.

    What other advice do I have?

    I rate this solution a ten out of ten. It is a very good solution that improves our performance. However, it would be helpful to include flow diagrams via logic apps in the next release.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Roshan George Thallamore - PeerSpot reviewer
    Azure DevOps and Cloud Lead at a consultancy with self employed
    Real User
    Top 5
    Is ideal for lifting and shifting monolithic applications to the cloud but deployment needs improvement
    Pros and Cons
    • "The most valuable feature is that it's an ideal solution when it comes to lifting and shifting monolithic applications from on-premises to Azure Cloud. It allows for a quick shift into the cloud without having to analyze and design very specific infrastructure and services for monolithic applications hosted primarily on-premises. Let's say that the team does not want to really redesign monoliths in a microservices-based application and that they want to make a quick move towards adopting the cloud tech stack. Then, Microsoft Azure App Service is probably the best option."
    • "In terms of room for improvement, ease of deployment would be an area that needs some focus. Azure does provide out-of-the-box deployment features, but I found that deploying to an App Service instance can be better in terms of more tools that could be available to perform a deployment."

    What is our primary use case?

    One use case was to host the Azure Bot logic code. The Bot logic was hosted on an App Service instance. The other use case was a POC where we were lifting and shifting a monolithic application, a .NET monolithic application, onto the cloud.

    What is most valuable?

    The most valuable feature is that it's an ideal solution when it comes to lifting and shifting monolithic applications from on-premises to Azure Cloud. It allows for a quick shift into the cloud without having to analyze and design very specific infrastructure and services for monolithic applications hosted primarily on-premises. Let's say that the team does not want to really redesign monoliths in a microservices-based application and that they want to make a quick move towards adopting the cloud tech stack. Then, Microsoft Azure App Service is probably the best option.

    What needs improvement?

    In terms of room for improvement, ease of deployment would be an area that needs some focus. Azure does provide out-of-the-box deployment features, but I found that deploying to an App Service instance can be better in terms of more tools that could be available to perform a deployment.

    For how long have I used the solution?

    I've been using this solution since 2020.

    It is deployed on a virtual network on Azure.

    What do I think about the stability of the solution?

    It is stable, but it really depends on the workload that is being shifted and the base service plan that is selected. Because though it is a platform as a service, you do have the option to design a service plan that is adequate for your applications, performance needs, and overall traffic that hits your applications. In terms of it being a platform-as-a-service feature, it is quite stable.

    What do I think about the scalability of the solution?

    It is scalable. The user base for the Bot service application was about 400 to 500 users worldwide.

    How are customer service and support?

    The technical support is average, and I would give them a six out of ten.

    How would you rate customer service and support?

    Neutral

    How was the initial setup?

    The initial setup is easy and can be done quickly depending on the number of applications being deployed. A single application should not take more than a couple of minutes to deploy.

    What's my experience with pricing, setup cost, and licensing?

    The cost depends on the App Service plan that you choose. There are a number of tiers available.

    What other advice do I have?

    If you have a standard enterprise application, for example, for the sake of simplicity, a single server with 50 requests per second, trying to do a lift and shift to App Service is probably a good idea. Bot framework solutions generally tend to use App Service for custom Bot logic, for hosting the custom Bots and the custom logic for Bots. App Service is probably a bit easier in terms of implementation compared to that of other options.

    However, for high performance applications that have a heavy load on them and are expected to perform at a certain level of response time, a pure lift and shift to App Service will not work well. You would probably need to choose a higher tier of App Service with a good App Service plan with a certain number of underlying host servers that are servicing it.

    Overall, I would rate Microsoft Azure App Service at six on a scale from one to ten.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Mouly Korthiwada - PeerSpot reviewer
    Enterprise Architect at Tata Consultancy Services
    Real User
    Top 5
    Flexible, configurable, and easy to use
    Pros and Cons
    • "The cost is reasonable."
    • "From an IoT use case perspective, we're all good, however, we should have additional plugins."

    What is our primary use case?

    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.

    What is most valuable?

    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. 

    What needs improvement?

    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.

    For how long have I used the solution?

    We started using the solution in 2021.

    What do I think about the stability of the solution?

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

    What do I think about the scalability of the solution?

    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. 

    Which solution did I use previously and why did I switch?

    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.

    How was the initial setup?

    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. 

    What's my experience with pricing, setup cost, and licensing?

    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. 

    What other advice do I have?

    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. 

    Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
    Flag as inappropriate
    PeerSpot user
    Ahmed Akanni - PeerSpot reviewer
    Azure App Service Technical Supprt Engineer at Tek Experts
    Real User
    Top 10
    A great solution for hosting web apps, and it is very easy to use
    Pros and Cons
    • "It is the best because it's easy to use, and there's a plan for every type of workload."
    • "Sometimes customer service and support can be challenging."

    What is our primary use case?

    Our primary use case for this solution is for hosting web apps so people can deploy this application and host it on an app service.

    What is most valuable?

    We have found the scalability feature most valuable. When you host an application on Microsoft Azure App Service and have a lot of users, there are times that there will be high traffic. High traffic is when many people try to access the Microsoft Azure App Service simultaneously. So Microsoft Azure App Service can scale up to meet the demand of those trying to access it. It has been at approximately 98% availability, and if any maintenance is required, it will notify you. You can find an alternative solution and use multiple instances to mitigate the downtime.

    What needs improvement?

    For now, I don't think there are any improvements to highlight.

    For how long have I used the solution?

    We have been using this solution for approximately a year and a half.

    How are customer service and support?

    We have had a fun experience with customer service and support, but sometimes customer service and support can be challenging. However, all the challenges we face are related to technology.

    How was the initial setup?

    There are two options for setting up the CLI shop and the portal. In terms of the portal, you can easily create an app service from the Azure portal. Some people are comfortable using the CLI shop, and some don't like going to the portal and creating the app service. I believe Azure did very well in that aspect.

    What's my experience with pricing, setup cost, and licensing?

    The pricing is quite fair because of its scalability. Before you choose the type of plan you want, you should look at the workloads that the apps have and what your organization needs. For example, if you have minimal traffic, you can use the basic plan. There's a plan for every type of workload which determines the subscription cost.

    What other advice do I have?

    I rate this solution nine out of ten. The solution is good. If somebody is considering using Microsoft Azure App Service, it is the best because it's easy to use, and there's a plan for every type of workload. Some features can give you certificates for the domain. If you already have an existing domain, you can bring it in to do it from Azure. Additionally, you can buy your domain and bind it to Azure, but if you already have an existing third-party domain, you can also use it with Azure.

    Disclosure: My company has a business relationship with this vendor other than being a customer:
    Flag as inappropriate
    PeerSpot user
    Akinwale Awoyele - PeerSpot reviewer
    DevOps Engineer at United States of Africa
    Real User
    Top 10
    A complete solution, with a large number of features that are easy to use, but require some prior learning to fully benefit from
    Pros and Cons
    • "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 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."

    What is our primary use case?

    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.

    What is most valuable?

    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.

    What needs improvement?

    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.

    For how long have I used the solution?

    We have been using this solution for four years.

    What do I think about the stability of the solution?

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

    What do I think about the scalability of the solution?

    This is an easily scalable solution.

    How are customer service and support?

    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.

    How would you rate customer service and support?

    Positive

    How was the initial setup?

    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.

    What's my experience with pricing, setup cost, and licensing?

    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.

    What other advice do I have?

    I would rate this solution an eight out of ten.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Microsoft Azure
    Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
    Flag as inappropriate
    PeerSpot user
    Buyer's Guide
    Download our free Microsoft Azure App Service Report and get advice and tips from experienced pros sharing their opinions.
    Updated: November 2022
    Buyer's Guide
    Download our free Microsoft Azure App Service Report and get advice and tips from experienced pros sharing their opinions.