What advice do you have for others considering Microsoft Azure App Service?

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 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.

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.

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

Overall, I would rate it eight out of ten.

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.

Even with all of its limitations, Microsoft Azure App Service is good. Overall, I rate the solution a nine out of ten.

The solution requires one person for maintenance. Some of their responsibilities are updating the code and deploying the web app. If you need to quickly set up and run an application without incurring any setup costs, this is the way to go. With this approach, you don't need to install or run anything on-premise. Simply create the application and start using it - the setup process is straightforward and fast. I rate Microsoft Azure App Service a ten out of ten.

We are end-users and customers. I'd rate the solution six out of ten. It's useful for companies that use iPads.

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.

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.

I rate Microsoft Azure App Services seven out of 10. To use the product, you need to be trained in Microsoft solutions because they all work closely together, though they are compatible with the other services. However, Azure does have a high density of Microsoft-native products. If a person does not have a strong background in Microsoft products, they will struggle initially. It will be easier with some foundational knowledge.

I would recommend this solution to others. I rate Microsoft Azure App Service an eight out of ten.

I would recommend this solution to others. I rate Microsoft Azure App Service a ten out of ten.

I'm working on Microsoft Azure App Service, end-to-end security such as Amazon GuardDuty, and AWS Security Hub. My company uses SQL services, AWS RDS, PaaS, and SaaS. My team also works on all Microsoft Defender for Cloud, Azure WAF, Azure Network Watcher, and Azure Service Map modules. My company works on endpoint security and related solutions, such as Microsoft Purview Compliance Manager and Microsoft Purview DLP. Microsoft Azure App Service is a mobile development platform. It's a serverless environment. My company has an interconnection with Microsoft Azure App Service, with API calls coming from the platform, so there's no specific user but a service account used by the company. My rating for Microsoft Azure App Service is seven out of ten based on the features used within the company. My company is a customer of Microsoft Azure App Service.

I rate the solution an eight out of ten.

I would recommend App Service to other users and rate it eight out of ten.

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.

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.

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.

This is a good solution for those who want to start small looking for a data center that is cloud based. I would rate this solution a nine out of ten.

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.

I would rate Azure App Services as eight out of ten.

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

Everything looks good and we are happy with this product. It seems to have everything that we need and I haven't seen any limitations. My advice to anybody who is looking at it is that it's a good platform to start building your integrations. I would rate this solution a ten out of ten.

We're a Microsoft partner. I'd advise other users just to be sure that they have all of the components on the Azure side in order to do the hybrid configuration. From my experience, that will give you better performance if you have everything on there. That, and it will be totally clear and you won't mix anything up with some private stuff. Overall, I'd rate the solution nine out of ten.

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.

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.

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.

My advice to others would be to occupy the use cases from businesses to see if this works for you. It is really easy. I give this solution a nine out of ten. In the future, I would like to have a template for development, though.

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.