Azure Container Apps
An Azure service that provides a general-purpose, serverless container platform.
691 questions
The api version you use for Microsoft.App is deprecated, please use latest api version
![](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(76.8, 21%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3E8%3C/text%3E%3C/svg%3E)
85989021
35
Reputation points
How to I update the Api's of the container app? I did the Patch but they are still not updated. I also updated my bicep template to reflect the 2023-05-01 api version
Azure Container Apps
{count} votes
-
Vinodh247 34,666 Reputation points MVP Volunteer Moderator2023-09-12T04:43:09.5933333+00:00 Hi 85989021:
whats the latest version available for this and how long after update you checked and found that it didnt reflect? also did you use the following instructions while updating?
https://learn.microsoft.com/en-us/rest/api/containerapps/stable/container-apps/update?tabs=HTTP
-
85989021 35 Reputation points
2023-09-12T10:54:32.9933333+00:00 Api version I used was 2023-05-01. I Just checked again this morning and it's still not changed. Yes, I used the instructions you noted above
-
MayankBargali-MSFT 70,941 Reputation points Moderator2023-09-12T11:29:04.0933333+00:00 @85989021 Thanks for reaching out.
I see that you have mentioned "The api version you use for Microsoft.App is deprecated, please use latest api version". Are you getting the error when you have tried to use api-version=2023-05-01 with the container update PATCH API?
The I see your another comment "Just checked again this morning and it's still not changed" so does it mean that the API returns 200 responses but the changes was not reflected which you passed in the body?
Please share more details on the request body what you have passed and what didn't reflected?
-
85989021 35 Reputation points
2023-09-12T12:02:17.1666667+00:00 I used the https://learn.microsoft.com/en-us/rest/api/containerapps/stable/container-apps/update?tabs=HTTP to updated and it returned a 202.
Body: {
"location": "East US"
}
Results:
api-supported-versions: 2022-01-01-preview, 2022-03-01, 2022-06-01-preview, 2022-10-01, 2022-11-01-preview, 2023-04-01-preview, 2023-05-01, 2023-05-02-preview, 2023-08-01-preview
cache-control: no-cache
content-length: 0
date: Tue, 12 Sep 2023 12:00:21 GMT
expires: -1
location: https://management.azure.com/subscriptions/......
pragma: no-cache
retry-after: 5
server: Microsoft-IIS/10.0
x-ms-correlation-request-id: 056d239b-191f-4cbd-a4c1-fbc21f00144e
x-ms-ratelimit-remaining-subscription-resource-requests: 699
x-ms-request-id: 056d239b-191f-4cbd-a4c1-fbc21f00144e
x-ms-routing-request-id: EASTUS:20230912T120021Z:056d239b-191f-4cbd-a4c1-fbc21f00144e
x-powered-by: ASP.NET
-
MayankBargali-MSFT 70,941 Reputation points Moderator
2023-09-14T02:47:26.9133333+00:00 @85989021 You can update the api-version in parameter section as below with any of the supported APIs as per your response error to resolve the issue for your region.
2022-01-01-preview, 2022-03-01, 2022-06-01-preview, 2022-10-01, 2022-11-01-preview, 2023-04-01-preview, 2023-05-01, 2023-05-02-preview, 2023-08-01-preview
-
85989021 35 Reputation points
2023-09-14T10:31:03.53+00:00 I did add the api-version as it is requried
-
MayankBargali-MSFT 70,941 Reputation points Moderator
2023-09-14T10:37:59.2366667+00:00 @85989021 I can see 202 response (Accepted response) and don't see the error that you have shared. I am confused what is your actual issue
The changes are not reflected to your container app when you get 202 error, or you are getting the error message as shared previously which is resolved now or the feedback to the document?
-
85989021 35 Reputation points
2023-09-14T12:00:08.32+00:00 As noted in my first post, there is no error. I get the 202 but the api version isn't updated when I check the portal. It's still the old version. I also removed the resource and tried to add it back with the new version but that didn't work either. It's still the version that is getting deprecated.
-
MayankBargali-MSFT 70,941 Reputation points Moderator
2023-09-15T03:23:37.0833333+00:00 @85989021 Can you help with the below question to understand more.
- Which blade (under the container apps) in the azure portal you have referred to in your screenshot?
- The API version that you are referring to (2022-11-01-preview) is the API for the Azure management API. Can you share the document that confirms that 2022-11-01-preview version is getting deprecated?
- I only see location in your request body previous screenshot and don't see any other version specifically for your container apps.
Looks like there is confusion that when you hit the endpoint with any of the API version then that API version will be reflected in your screenshot. These are the management endpoint with different code repro and doesn't mean that it will be reflected in the screenshot that you have shared.
-
85989021 35 Reputation points
2023-09-15T14:41:31.3466667+00:00 - blade
- deprecated:
Since I don't need to update anything else but the api version the containerApp is using, I didn't add any other container information.
-
MayankBargali-MSFT 70,941 Reputation points Moderator
2023-09-19T01:27:38.0066667+00:00 @85989021 In your ARM/bicep template for the Microsoft.App/containerapps resource you need to use the latest supported apiverson. You can do the incremental deployment of your template to update the version or redeploy your bicep template. The update API will not change the API version in your ARM/bicep template.
-
85989021 35 Reputation points
2023-09-19T12:21:13.95+00:00 I already tried both those ways and it didn't work. My bicep template has the 2023-05-01 version.
-
MayankBargali-MSFT 70,941 Reputation points Moderator
2023-09-20T01:03:25.2266667+00:00 @85989021 This would need to review the backend logs why your increment deployment/redeployment bicep template didn't update the API version. I will suggest you to create one on one support ticket so this can be reviewed further. In case if you don't have the support plan then please let me know.
-
85989021 35 Reputation points
2023-09-20T10:40:49.7633333+00:00 We don't have a support plan at this time.
-
85989021 35 Reputation points
2023-09-20T10:41:26.8233333+00:00 We don't have a support Plan at the moment.
-
MayankBargali-MSFT 70,941 Reputation points Moderator
2023-09-20T11:50:12.8+00:00 @85989021 Please send an email with subject line “Attn:Mayank” to AzCommunity[at]Microsoft[dot]com with your subscription ID so I can enable one time support request on your subscription.
-
85989021 35 Reputation points
2023-09-20T12:22:30.2166667+00:00 Just sent you a message.
-
85989021 35 Reputation points
2023-10-30T16:02:15.16+00:00 Any word on this issue. I received another email today about Retirement of Azure Container Apps API versions 2022-06-01-preview and 2022-11-01-preview
Sign in to comment
Sign in to answer