s["@odata.type"] is not a function. (In 's["@odata.type"]()', 's["@odata.type"]' is undefined) In Portal

Question

s["@odata.type"] is not a function. (In 's["@odata.type"]()', 's["@odata.type"]' is undefined) In Portal

After adding a rule to my Azure CDN portal started to show s["@odata.type"] is not a function. (In 's["@odata.type"]()', 's["@odata.type"]' is undefined) In the information view and the rules engine view.

Does anyone know how can I fix it?

So basically is not manageable anymore and in order to request support Microsoft wants to bill me a support ticket and I think is not acceptable because is not something I requested asking for help to use the portal, is something caused by bad implementation.

KapilAnanth-MSFT 11,611 Reputation points Microsoft Employee

2022-08-12T04:14:54.743+00:00
Hi @Rodrigo Fraga Olvera ,

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
I understand that you are seeing a notification stating "s["@odata.type"] is not a function" in Azure Portal.

Can you please confirm if you are not using the Azure Portal in Preview mode?

If you are using the Preview Portal, request you to use the normal portal.

Azure portal public: https://portal.azure.com/#home OR https://portal.azure.com/?feature.customportal=false#home

Please feel free to let us know if the issue still prevails.

Cheers,
Kapil.

----------------------------------------------------------------------------------------------------------------

Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.
Jorrit Geerlings 1 Reputation point

2022-08-12T08:28:52.593+00:00

Same problem here. But here it also arises in an endpoint where I didn't make any changes. Yesterday everything was working fine, but this morning I noticed.
Ludovic Fernandez 1 Reputation point

2022-08-12T09:07:48.757+00:00

Same issue here using the normal portal.
Jibin K Benny-FT 1 Reputation point

2022-08-12T09:44:37.13+00:00

anonymous user-MSFT Hello, we are also experiencing the same issue. We have tried with Azure portal not the preview version.
Anonymous

2022-08-12T10:02:32.907+00:00

Same here while using normal portal.
Anonymous

2022-08-12T10:03:07.24+00:00

Same here using normal portal.
Kari Bishop 1 Reputation point

2022-08-12T10:40:31.47+00:00

I'm having the same issue and we are doing a deployment! We are unable to access any of the settings for our cdn end points. Specifically we need to update the Rules Engine and all pages get the error: s.@odata.type is not a function
Kari Bishop 1 Reputation point

2022-08-12T10:42:37.857+00:00

Your suggestion does not work. There is an error in the portal. Please provide a resolution so we can finish our updates.
KapilAnanth-MSFT 11,611 Reputation points Microsoft Employee

2022-08-12T10:54:33.887+00:00

Hi everyone,

Thanks for your comments.

I shall check internally and update this thread.

Thanks,
Kapil.
KapilAnanth-MSFT 11,611 Reputation points Microsoft Employee

2022-08-12T13:45:03.68+00:00

Hello everyone,

I checked this internally and it seems it is reproducible by a few of our customers and internal subscriptions.

I shall keep this thread updated once we have a fix.

Meanwhile, I request you to raise a support ticket if you should require immediate assistance.

Thanks,
Kapil
Yuri Suarez 6 Reputation points

2022-08-12T14:56:44.173+00:00

I'm having the same error after creating a rule in "Rules engine" of cdn endpoint.
Yuri Suarez 6 Reputation points

2022-08-12T15:02:06.113+00:00

Same for me, using normal portal doesn't fix the issue. I need to create new rules and I can't go forward, please advice any other solution.
Francisco Leyva 36 Reputation points

2022-08-12T18:06:27.267+00:00

Same problem here, other team members started to experience the issue a few days ago and today it happened to me as well.

I'm no longer able to access the "Overview" or the "Rules Engine" sections in the Azure portal for the CDN configuration page:
Victor H 1 Reputation point

2022-08-12T19:09:44.597+00:00

Same here; I am not on the preview portal
Suresh Gedela 16 Reputation points

2022-08-12T21:22:44.943+00:00

anonymous user-MSFT we are facing this issue again and again. Could you please look at this as we are blocked from adding CDN rules affecting our business.
Suresh Gedela 16 Reputation points

2022-08-12T21:26:33.513+00:00

anonymous user-MSFT we are facing this issue again and again. Could you please look at this as we are blocked from adding CDN rules affecting our business.
Rayhaan Olli 6 Reputation points

2022-08-13T03:33:49.37+00:00

Having the same problem...
I created rules and now i need to modify them but i see the s["@odata.type"] is not a function. in the rules engine section
Matt 11 Reputation points

2022-08-13T07:27:55.52+00:00

The same here after creating a rule in Rules Engine of CDN Endpoint.
Mike Bundy 11 Reputation points

2022-08-13T08:05:54.753+00:00

Having the same issue - all of my CDN Endpoints - of which I have 40+ - are unmanageable from the portal, because they throw an error in the Overview and Rules sections - s.@odata.type is not a function - which is coming from a Javascript promise in Microsoft's code.
rucio 6 Reputation points

2022-08-13T13:26:35.163+00:00

I got a error message "s.@odata.type is not a function".
I can not purge my CDN caches in edges now.
I tried using InPrivate window of Edge, but same result.

I have submitted a support request.
Robert 1 Reputation point

2022-08-13T18:44:02.947+00:00

Same problem please address
Robert 1 Reputation point

2022-08-13T18:44:11.37+00:00

Same problem please address
SDSS 6 Reputation points

2022-08-14T05:33:24.087+00:00

I am facing the same issue. Yesterday, everything was working just fine...
Huisman, Peter 6 Reputation points

2022-08-14T07:11:08.56+00:00

Same here...

s.@odata.type is not a function
Ryan Yin 6 Reputation points

2022-08-14T08:10:56.19+00:00

same here...
Mike Bundy 11 Reputation points

2022-08-15T06:29:37.5+00:00

This is a major problem for me at the moment, as I can't maintain my client's CDNs. I am running a fully paid subscription, which is up-to-date.
Daniel Stenson 1 Reputation point

2022-08-15T08:36:46.007+00:00

Facing the same issue here. Any fix or troubleshooting steps would be greatly appreciated.
Pot, Robby 11 Reputation points

2022-08-15T12:50:25.24+00:00

Your suggestion does not fix the problem.
Petrosyan Ruben 6 Reputation points

2022-08-15T13:19:01.407+00:00

Any update on this issue?
Douglas Oliveira 6 Reputation points

2022-08-15T14:06:34.07+00:00

Same here, this message appears in all my CDN profiles:
Robert 1 Reputation point

2022-08-15T15:49:07.047+00:00

Updates would be awesome
Ryan 1 Reputation point

2022-08-15T19:45:59.537+00:00

Hello,

We are also having an issue managing our CDN's as well due to the same error message. Is there an ETA for a resolution?

Thank you for your help!
Ryan 1 Reputation point

2022-08-15T19:46:05.737+00:00

Hello,

We are also having an issue managing our CDN's as well due to the same error message. Is there an ETA for a resolution?

Thank you for your help!
Yuri Suarez 6 Reputation points

2022-08-15T19:55:54.463+00:00

I'm waiting for updates as well
Robert 1 Reputation point

2022-08-15T23:28:33.573+00:00

anonymous user-MSFT is this being looked at?
Vincent Cotton 6 Reputation points

2022-08-16T03:02:23.127+00:00

I'm experiencing the same issue and it is preventing me from purging my CDN cache...
Matt 11 Reputation points

2022-08-16T03:57:20.577+00:00

Purge is still available from the Front Door and CDN profiles panel.
Matt 11 Reputation points

2022-08-16T04:01:21.25+00:00

Purge is still available from the Front Door and CDN profiles panel.
Rayhaan Olli 6 Reputation points

2022-08-16T04:44:11.837+00:00

Hi anonymous user-MSFT,

By when will the issue be resolved?

Regards,
Rayhaan
Victor H 1 Reputation point

2022-08-16T04:51:48.703+00:00

Hi Kapil,

When will this be fixed? It's crazy this hasn't been fixed after over 4 days.
Husnu Shen 1 Reputation point

2022-08-16T06:25:28.683+00:00

Same issue here,
anonymous user-MSFT any update on this issue?
KapilAnanth-MSFT 11,611 Reputation points Microsoft Employee

2022-08-16T06:36:18.26+00:00
Hello Everyone,

Thank you all for your comments.
Currently, there is no ETA on this.

I request you to please leverage Azure CLI or Powershell for managing the CDN resource.

CLI:

https://learn.microsoft.com/en-us/cli/azure/cdn/endpoint?view=azure-cli-latest

https://learn.microsoft.com/en-us/cli/azure/cdn?view=azure-cli-latest

Powershell:

https://learn.microsoft.com/en-us/azure/cdn/cdn-manage-powershell

https://learn.microsoft.com/en-us/powershell/module/az.cdn/?view=azps-8.2.0

Thanks,
Kapil.
Yuri Suarez 6 Reputation points

2022-08-16T18:06:35.997+00:00

When I try to add, remove or list a rule, I get an error:
Command group 'cdn endpoint rule' is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus
Yuri Suarez 6 Reputation points

2022-08-16T20:38:31.737+00:00

I was adding the wrong endpoint name. It works: az cdn endpoint rule show -g ResourceGroupName -n EndpointName --profile-name ProfileEndpointName
Vincent Cotton 6 Reputation points

2022-08-16T21:13:58.027+00:00

Thanks!
Mike Bundy 1 Reputation point

2022-08-17T01:49:18.5+00:00

FWIW - There is a fix release ETA on this now - Aug-22
Dian Yu 1 Reputation point

2022-08-17T03:29:44.417+00:00

I met the same issue yesterday and it worked well this morning out of thin air.
Very weird.....
And it seems like a portal issue but not CDN service bug....
KapilAnanth-MSFT 11,611 Reputation points Microsoft Employee

2022-08-17T04:12:35.54+00:00

Hi @Yuri Suarez ,

Are you able to use the 'cdn endpoint rule' after using the correct endpoint?

If not, please share the error message and I shall try to check the issue.

Cheers,
Kapil
Rohit Goyal 21 Reputation points

2022-08-17T04:14:35.033+00:00

Please give ETA fot this......we are stuck we are at delivery stage of product
Mike Bundy 1 Reputation point

2022-08-17T04:19:16.887+00:00

As per above - ETA is Aug-22 for the portal fix - interim solution is to install and use Azure Powershell.
Aurelijus Butkus 1 Reputation point

2022-08-17T06:18:16.747+00:00

Please use this URL as a workaround:
https://portal.azure.com/?microsoft_azure_cdn=staging
Yuri Suarez 6 Reputation points

2022-08-17T12:42:29.12+00:00

Hi anonymous user-MSFT,

After removing a rule from CLI, I was able to use the UI for rules. The issue was resolved. Thanks!

To list the endpoint:
az cdn endpoint list --resource-group YourResourceGroup --profile-name YourProfileNameEndpoint

To remove a rule:
az cdn endpoint rule remove -g YourResourceGroup -n YourEndpointName --profile-name YourProfileNameEndpoint --rule-name YourRuleName
Matt 11 Reputation points

2022-08-20T02:48:03.997+00:00

Looks like it is working again now!
Thanks MS.
Matt 11 Reputation points

2022-08-20T02:48:30.17+00:00

Looks like it is working again now!
Thanks MS.
Ryan 1 Reputation point

2022-08-22T13:32:59.62+00:00

Confirmed also working for me as well!

KapilAnanth-MSFT 11,611 Reputation points Microsoft Employee

2022-08-12T04:14:54.743+00:00

Hi @Rodrigo Fraga Olvera ,

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
I understand that you are seeing a notification stating "s["@odata.type"] is not a function" in Azure Portal.

Can you please confirm if you are not using the Azure Portal in Preview mode?

If you are using the Preview Portal, request you to use the normal portal.

Azure portal public: https://portal.azure.com/#home OR https://portal.azure.com/?feature.customportal=false#home

Please feel free to let us know if the issue still prevails.

Cheers,
Kapil.

----------------------------------------------------------------------------------------------------------------

Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.
Jorrit Geerlings 1 Reputation point

2022-08-12T08:28:52.593+00:00

Same problem here. But here it also arises in an endpoint where I didn't make any changes. Yesterday everything was working fine, but this morning I noticed.
Ludovic Fernandez 1 Reputation point

2022-08-12T09:07:48.757+00:00

Same issue here using the normal portal.
Jibin K Benny-FT 1 Reputation point

2022-08-12T09:44:37.13+00:00

anonymous user-MSFT Hello, we are also experiencing the same issue. We have tried with Azure portal not the preview version.
Anonymous

2022-08-12T10:02:32.907+00:00

Same here while using normal portal.
Anonymous

2022-08-12T10:03:07.24+00:00

Same here using normal portal.
Kari Bishop 1 Reputation point

2022-08-12T10:40:31.47+00:00

I'm having the same issue and we are doing a deployment! We are unable to access any of the settings for our cdn end points. Specifically we need to update the Rules Engine and all pages get the error: s.@odata.type is not a function
Kari Bishop 1 Reputation point

2022-08-12T10:42:37.857+00:00

Your suggestion does not work. There is an error in the portal. Please provide a resolution so we can finish our updates.
KapilAnanth-MSFT 11,611 Reputation points Microsoft Employee

2022-08-12T10:54:33.887+00:00

Hi everyone,

Thanks for your comments.

I shall check internally and update this thread.

Thanks,
Kapil.
KapilAnanth-MSFT 11,611 Reputation points Microsoft Employee

2022-08-12T13:45:03.68+00:00

Hello everyone,

I checked this internally and it seems it is reproducible by a few of our customers and internal subscriptions.

I shall keep this thread updated once we have a fix.

Meanwhile, I request you to raise a support ticket if you should require immediate assistance.

Thanks,
Kapil
Yuri Suarez 6 Reputation points

2022-08-12T14:56:44.173+00:00

I'm having the same error after creating a rule in "Rules engine" of cdn endpoint.
Yuri Suarez 6 Reputation points

2022-08-12T15:02:06.113+00:00

Same for me, using normal portal doesn't fix the issue. I need to create new rules and I can't go forward, please advice any other solution.
Francisco Leyva 36 Reputation points

2022-08-12T18:06:27.267+00:00

Same problem here, other team members started to experience the issue a few days ago and today it happened to me as well.

I'm no longer able to access the "Overview" or the "Rules Engine" sections in the Azure portal for the CDN configuration page:
Victor H 1 Reputation point

2022-08-12T19:09:44.597+00:00

Same here; I am not on the preview portal
Suresh Gedela 16 Reputation points

2022-08-12T21:22:44.943+00:00

anonymous user-MSFT we are facing this issue again and again. Could you please look at this as we are blocked from adding CDN rules affecting our business.
Suresh Gedela 16 Reputation points

2022-08-12T21:26:33.513+00:00

anonymous user-MSFT we are facing this issue again and again. Could you please look at this as we are blocked from adding CDN rules affecting our business.
Rayhaan Olli 6 Reputation points

2022-08-13T03:33:49.37+00:00

Having the same problem...
I created rules and now i need to modify them but i see the s["@odata.type"] is not a function. in the rules engine section
Matt 11 Reputation points

2022-08-13T07:27:55.52+00:00

The same here after creating a rule in Rules Engine of CDN Endpoint.
Mike Bundy 11 Reputation points

2022-08-13T08:05:54.753+00:00

Having the same issue - all of my CDN Endpoints - of which I have 40+ - are unmanageable from the portal, because they throw an error in the Overview and Rules sections - s.@odata.type is not a function - which is coming from a Javascript promise in Microsoft's code.
rucio 6 Reputation points

2022-08-13T13:26:35.163+00:00

I got a error message "s.@odata.type is not a function".
I can not purge my CDN caches in edges now.
I tried using InPrivate window of Edge, but same result.

I have submitted a support request.
Robert 1 Reputation point

2022-08-13T18:44:02.947+00:00

Same problem please address
Robert 1 Reputation point

2022-08-13T18:44:11.37+00:00

Same problem please address
SDSS 6 Reputation points

2022-08-14T05:33:24.087+00:00

I am facing the same issue. Yesterday, everything was working just fine...
Huisman, Peter 6 Reputation points

2022-08-14T07:11:08.56+00:00

Same here...

s.@odata.type is not a function
Ryan Yin 6 Reputation points

2022-08-14T08:10:56.19+00:00

same here...
Mike Bundy 11 Reputation points

2022-08-15T06:29:37.5+00:00

This is a major problem for me at the moment, as I can't maintain my client's CDNs. I am running a fully paid subscription, which is up-to-date.
Daniel Stenson 1 Reputation point

2022-08-15T08:36:46.007+00:00

Facing the same issue here. Any fix or troubleshooting steps would be greatly appreciated.
Pot, Robby 11 Reputation points

2022-08-15T12:50:25.24+00:00

Your suggestion does not fix the problem.
Petrosyan Ruben 6 Reputation points

2022-08-15T13:19:01.407+00:00

Any update on this issue?
Douglas Oliveira 6 Reputation points

2022-08-15T14:06:34.07+00:00

Same here, this message appears in all my CDN profiles:
Robert 1 Reputation point

2022-08-15T15:49:07.047+00:00

Updates would be awesome
Ryan 1 Reputation point

2022-08-15T19:45:59.537+00:00

Hello,

We are also having an issue managing our CDN's as well due to the same error message. Is there an ETA for a resolution?

Thank you for your help!
Ryan 1 Reputation point

2022-08-15T19:46:05.737+00:00

Hello,

We are also having an issue managing our CDN's as well due to the same error message. Is there an ETA for a resolution?

Thank you for your help!
Yuri Suarez 6 Reputation points

2022-08-15T19:55:54.463+00:00

I'm waiting for updates as well
Robert 1 Reputation point

2022-08-15T23:28:33.573+00:00

anonymous user-MSFT is this being looked at?
Vincent Cotton 6 Reputation points

2022-08-16T03:02:23.127+00:00

I'm experiencing the same issue and it is preventing me from purging my CDN cache...
Matt 11 Reputation points

2022-08-16T03:57:20.577+00:00

Purge is still available from the Front Door and CDN profiles panel.
Matt 11 Reputation points

2022-08-16T04:01:21.25+00:00

Purge is still available from the Front Door and CDN profiles panel.
Rayhaan Olli 6 Reputation points

2022-08-16T04:44:11.837+00:00

Hi anonymous user-MSFT,

By when will the issue be resolved?

Regards,
Rayhaan
Victor H 1 Reputation point

2022-08-16T04:51:48.703+00:00

Hi Kapil,

When will this be fixed? It's crazy this hasn't been fixed after over 4 days.
Husnu Shen 1 Reputation point

2022-08-16T06:25:28.683+00:00

Same issue here,
anonymous user-MSFT any update on this issue?
KapilAnanth-MSFT 11,611 Reputation points Microsoft Employee

2022-08-16T06:36:18.26+00:00

Hello Everyone,

Thank you all for your comments.
Currently, there is no ETA on this.

I request you to please leverage Azure CLI or Powershell for managing the CDN resource.

CLI:

https://learn.microsoft.com/en-us/cli/azure/cdn/endpoint?view=azure-cli-latest

https://learn.microsoft.com/en-us/cli/azure/cdn?view=azure-cli-latest

Powershell:

https://learn.microsoft.com/en-us/azure/cdn/cdn-manage-powershell

https://learn.microsoft.com/en-us/powershell/module/az.cdn/?view=azps-8.2.0

Thanks,
Kapil.
Yuri Suarez 6 Reputation points

2022-08-16T18:06:35.997+00:00

When I try to add, remove or list a rule, I get an error:
Command group 'cdn endpoint rule' is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus
Yuri Suarez 6 Reputation points

2022-08-16T20:38:31.737+00:00

I was adding the wrong endpoint name. It works: az cdn endpoint rule show -g ResourceGroupName -n EndpointName --profile-name ProfileEndpointName
Vincent Cotton 6 Reputation points

2022-08-16T21:13:58.027+00:00

Thanks!
Mike Bundy 1 Reputation point

2022-08-17T01:49:18.5+00:00

FWIW - There is a fix release ETA on this now - Aug-22
Dian Yu 1 Reputation point

2022-08-17T03:29:44.417+00:00

I met the same issue yesterday and it worked well this morning out of thin air.
Very weird.....
And it seems like a portal issue but not CDN service bug....
KapilAnanth-MSFT 11,611 Reputation points Microsoft Employee

2022-08-17T04:12:35.54+00:00

Hi @Yuri Suarez ,

Are you able to use the 'cdn endpoint rule' after using the correct endpoint?

If not, please share the error message and I shall try to check the issue.

Cheers,
Kapil
Rohit Goyal 21 Reputation points

2022-08-17T04:14:35.033+00:00

Please give ETA fot this......we are stuck we are at delivery stage of product
Mike Bundy 1 Reputation point

2022-08-17T04:19:16.887+00:00

As per above - ETA is Aug-22 for the portal fix - interim solution is to install and use Azure Powershell.
Aurelijus Butkus 1 Reputation point

2022-08-17T06:18:16.747+00:00

Please use this URL as a workaround:
https://portal.azure.com/?microsoft_azure_cdn=staging
Yuri Suarez 6 Reputation points

2022-08-17T12:42:29.12+00:00

Hi anonymous user-MSFT,

After removing a rule from CLI, I was able to use the UI for rules. The issue was resolved. Thanks!

To list the endpoint:
az cdn endpoint list --resource-group YourResourceGroup --profile-name YourProfileNameEndpoint

To remove a rule:
az cdn endpoint rule remove -g YourResourceGroup -n YourEndpointName --profile-name YourProfileNameEndpoint --rule-name YourRuleName
Matt 11 Reputation points

2022-08-20T02:48:03.997+00:00

Looks like it is working again now!
Thanks MS.
Matt 11 Reputation points

2022-08-20T02:48:30.17+00:00

Looks like it is working again now!
Thanks MS.
Ryan 1 Reputation point

2022-08-22T13:32:59.62+00:00

Confirmed also working for me as well!

Answer 1

KapilAnanth-MSFT 11,611 Microsoft Employee

Hello everyone,

The current ETA for the fix is by 22nd August.

In the meantime, you can use the following portal URL: https://portal.azure.com/?microsoft_azure_cdn=staging to workaround this.

Azure Powershell and Azure CLI should work nevertheless

Thanks,
Kapil

-------------------------------------------------------------------------------------

Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer

Ryan 1 Reputation point

2022-08-17T14:44:50.083+00:00

Appreciate the update and ETA - thank you!
Robert 1 Reputation point

2022-08-17T16:22:02.533+00:00

Thanks for eta

s["@odata.type"] is not a function. (In 's["@odata.type"]()', 's["@odata.type"]' is undefined) In Portal

1 answer

Activity