The initial setup is straightforward. Setting up an instance of Azure API Management in the cloud is as simple as setting up Azure. It would probably take around 30 minutes to spin up the service, and you can use it. However, using the gateway in your projects is an ongoing process. If you just want to set up a gateway, it will probably be quick and easy.

When it comes to the deployment process, it's a cloud solution, so you can use infrastructure as code using Azure Visor or ARM templates or follow different infrastructure support solutions to be able to deploy the solution on your own public cloud subscription.

Microsoft Azure API Management is effortless to set up. It has a brilliant setup.

It took me just two weeks to set up Microsoft Azure API Management.

I'd rate its setup a four out of five.

The initial setup is easy. Deployment itself is straightforward, technically speaking, but the high cost is a major drawback. It's not exactly budget-friendly.

It takes work. One needs to learn about this tool, the policies, and how to work with them.

The initial setup is straightforward. It was an organization-wide integration, so we have never faced any issues.

The initial setup wasn't entirely straightforward or altogether complex. It was somewhere in the middle.

On a scale from one to five, I would give the initial setup of Microsoft Azure API Management a three. For me, AWS is two, and Microsoft is three.

I would rate the initial setup an eight out of ten, where one is difficult and ten is easy. Previously, we were using Apigee, so comparing it to that, it's cloud-specific and opens the gateway. So there were some challenges.

I would rate the initial setup process a four out of five.  The setup was basic and good.

The initial setup is very easy. It's not complex at all. 

The initial setup of Microsoft Azure API Management is straightforward. However, we had an issue with the DSTV upgrade. It has its own logic of what to decide. 

The full implementation process of the solution takes time, approximately six hours.

To deploy Microsoft Azure API Management, we utilize TerraForm to incorporate modules that cover all departments. These modules have already been created, so we simply provide the necessary parameters and execute the pipeline. Consequently, we do not rely on the Azure portal for this process and instead rely solely on Azure automation.

I rate the initial setup of Microsoft Azure API Management a nine out of ten.

Deploying API Management is somewhat tricky depending on your level of technical knowledge. The first time we used it in production, we had it for a couple of months. The first month was an evaluation period, so we had it in a test environment to get a feel for how it works and possible complications. However, you could deploy it in a couple of weeks if you wanted. 

You only need about two to manage it, including one admin. It's more like a platform-as-a-service, so we don't need to do the normal maintenance we do on an on-prem platform. 

The initial setup was pretty straightforward. 

I have a basic understanding of the API fundamentals. Those were what I was looking for; that's what I was looking for first, just to see if my understanding of the fundamentals. With my level of knowledge, it was fine. 

For someone with basic knowledge, you can deploy the solution within a week. 

There is some maintenance needed. However, that person is supposed to be someone who's more DevOps inclined.

The setup is very easy and doesn't take long. 

The solution's initial setup is pretty straightforward. However, more public documentation could have been available from other open communities. The solution is still being improved, and insufficient documentation is available on public forums.

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup a seven or seven and a half out of ten.

The initial setup is straightforward. 

The initial setup is very straightforward and simple. I'd rate the ease of deployment eight out of ten.

The provisioning takes a couple of minutes. Then you need to do some programming. 

API Management does not take long to deploy.

Because it is a cloud solution, the initial setup is straightforward.

The solution takes one hour to deploy. Like everything on Azure, it is difficult to create the deployment scripts because the ARM and Bicep that they use are awful. Deployment is very complex.

I would rate the experience of the setup of Azure API Management a two out of five.

The initial setup is not so straightforward and really depends on the landscape. If a customer has different business streams such as credit cards, debit cards, payment accounts and credit accounts it can be more complicated. Things have improved recently. Previously, a deployment could have taken up to 18 months.  We can now do a similar implementation in around six to eight months. 

The cloud deployment of Microsoft Azure API Management could be better.

The initial setup of Microsoft Azure API Management is straightforward. It took us approximately 30 minutes to complete.

I would rate the initial setup of Microsoft Azure API Management a four out of five.

I rate Microsoft Azure API Management a seven out of ten for the ease of its initial setup.

The initial setup is not complex as this is a PaaS-based solution.

Because we are trying to move away from the EDI, the initial setup wasn't that complex. The interfaces were already there in the EDI. This engagement is more to transform existing EDI-based approach to an API-based one. The business logic, more or less, is there. This initiative is more to help us decouple technical stack from the business process.

The API manager is managing the business interactions, whether it is the consumer onboarding or the customer decoupling them from the IT based EDI processing. 

The EDI would require that the customer technology team and the company technology team communicate and work together to integrate the interface. Whereas here you don't need to worry about it. It's simple as a business consumer signing up for an API, and all they need is a link to click and get the URL into their space and then they are done.

It's an easier way to integrate their API. If you want to make it into a more robust application, that's a different process, but consumption-wise it's easier. 

For those who do not want to integrate it into their applications, we have been giving them an application that they could just install from an App Store on their portal. This application will then expose the APIs available for use.  All they need to do is subscribe and get going.

Implementation was pretty simple in this particular engagement. We had a vision of how the API is going to be consumed and how many were needed. We paced ourselves in an agile model with a simplified storyboard and a proper velocity mapping of the activity.

It took anywhere from three to four weeks for each API to get them ready and we took it at our pace. We had released approximately ten API's in less than six months.

We had a six-member team for deployment, including the BA and project management. In the post-deployment, we only need three people to maintain.

The initial setup is easy. It takes a lot of time to deploy it. They are coming out with a feature that is supposed to shorten how long it takes.

The initial setup is more or less straightforward.

It took a couple of weeks to complete the entire migration from Amazon AWS to Microsoft Azure API Management.

The initial setup is straightforward. A company shouldn't have any problems during the process.

I give the initial setup an eight out of ten. The deployment took one business day. We require two people to complete the implementation.

I wasn't directly involved with the implementation, and I'm not sure how long it took to deploy the product. 

The initial setup was easy - it didn't take long, and the additional features were added normally.

The cloud-based version is not difficult to deploy. Microsoft Azure API Management's deployment depends on the API numbers customers want to onboard. It takes around four to six months. 

The initial setup is straightforward.

It was deployed very quickly.

You have to read about how to do it four or five times and then you can implement it. It's a publicly accessible API so it needs a security layer and then you can secure it. Otherwise, anybody can access it. You need proper controls, authentication, and authorization. You need to sort this out first. 

The initial setup of Microsoft Azure API Management took us three days.

Integration of this solution is easy. I won't call it an initial setup. It's an integration.

The initial setup was simple, with no complications, other than the configuration of the authentication in the API Management.

The installation process for Microsoft Azure API Management was easy.

The initial setup was quite easy as it is a managed service.

The initial setup is straightforward. It is very easy to set up.

Because everything is automated directly from our pipelines, maintenance is a very small task that we require.

It is very easy to deploy, and configure.

It's very straightforward to set it up. It really is. That's one of its strengths, that it's very easy to get started.

The versioning makes deployments more complicated than you would like, so you have to build some of your own toolings.

The initial setup was pretty straightforward. It took less than one day, around a couple of hours total. It's pretty quick. I deployed it myself with some product documentation. 

I would not say that the initial setup is easy or tough, but in the middle. It can be difficult in that you need to know the components in order to use this solution to its full extent.

The length of time required for deployment depends on the use case and what we are building. It can take a month or sometimes, three months.

The initial setup was very straightforward and simple. The deployment only took a few hours. 

The initial setup is straightforward.

Because you need to define the API contract, initially it may take about two months. However, this is not due to the Microsoft product.

The initial setup isn't too difficult and doesn't take too long. You need to handle it to have the management gateway. Of course, every time it is deployed, then it needs to be configured to work with API. That could take some time.

For the deployment and maintenance, the size of the team you need depends on the project. We had a couple of developers on ours, for example.

I did not participate in the installation. However, from the information I have received, it was quite difficult. It wasn't difficult because of the solution itself but because, for us, it was a totally new solution. We had no experience with it. If a company has a lot of experience with Azure API Management, it would be rather straightforward.

The tool's setup depends. If you use it in the CI/CD pipeline, then the setup is complex. To deploy the solution, you need to create a template and enable the features. 

You really need an expert to onboard the solution because it comes with more complexity than you might think. Also, internal teams often start playing with the solution during onboarding instead of sticking to best practices, which can result in having to start the process over again.

It is a straightforward setup. The implementation is not difficult or complex. The deployment is quick as well. It only took two or three days to get everything up and running.

We have about five technical people who can handle the setup and implementation process.

The setup and configuration are very quick.

The initial setup is very simple. Within a few days, one can understand completely how to use it. It does not require deployment because it is available on the cloud and everything is ready. In fact, there is no installation at all.

It will take some time to onboard your API and define your policies, such as those for security. It should take about ten minutes to get up and running.

Initial setup was fairly straightforward; excellent documentation.

Microsoft Azure API Management is easy to install.

We have a team of four engineers and managers to maintain this solution.

The initial setup is not that complex, but there are certain challenges.

The setup was straightforward, setting up a basic API management portal is only a few clicks in the Azure Portal. Once it is set up, the APIs can directly be added by just importing the Swagger file.

Pretty easy. The online documentation is very thorough.

The initial setup for us was easy. It helps that we have Azure knowledge within the company.

I believe the initial set up is straightforward via the Azure portal. But setting up the policies for the APIs and all of that, I can't say. I've had feedback from a colleague working with it that at some point he wished things would be easier but I don't have first hand experience. 

The initial setup is very simple. It doesn't take longer than one or two hours to deploy.