This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 93%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERA%3C/text%3E%3C/svg%3E)
I've successfully used ARM templates to update an API and deploy that update to an APIM tenant. I've been able to port an API to a different APIM tenant using the same process.
However, this isn't enough for my use-case. When I update an API this way, I'll need that update to be part of a brand new revision number, with that revision's CURRENT flag = false. Modifying the relevant fields in {APIName}-api.template.json ( apiRevision and isCurrent) doesn't seem to trigger the creation of a new revision. I believe revisions are their own resource type, and I'll have to create a new instance of that type that my API template will have to reference.
I'm having trouble finding documentation related to this. How can I accomplish this?
@Robert Abraham Just following up to see if my response helps
The name has to include a revision suffix like ;rev=n as mentioned in the reference docs. By default, the current revision is updated.
Here is the description that I am referring to for reference
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 84%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESG%3C/text%3E%3C/svg%3E)
Hi @Pramod Valavala the Link you have provided is not working, is there a newer Link? I am stuck with the same issue.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 87%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EOG%3C/text%3E%3C/svg%3E)
@Pramod Valavala @Sia Ghassemi I found an updated latest version url as - https://learn.microsoft.com/en-us/azure/templates/microsoft.apimanagement/2021-08-01/service/apis?tabs=bicep#microsoftapimanagementserviceapis-object but even in there, there is no mention of adding ;rev=n as such in name for the "Microsoft.ApiManagement/service/apis" resource type and in fact on setting the apiRevision property to say 3 and adding ;rev=3 in the name, the ARM deployment fails saying -
Error: Code=InvalidTemplate; Message=Deployment template validation failed: 'The resource
'Microsoft.ApiManagement/service/<serverName>/apis/<originalApiName>' is not defined in the template.
Creating a new revision via the ARM template is still not working. Please guide at earliest
@Sia Ghassemi @Omkar Ghaisas Apologies for not getting back sooner here! I've updated the link and here is the description that I am talking about for reference