All resources not listing up in resource group

SARASWAT CHETAN 91

When one click's on any resource group's and it by default open's up the Overview pane of the resource group and it should list out all the resources within the resource section, however only a section of resources are getting list up and when i scroll down the records section , the remaining resources are not visible.

So I zoom out my browser and some more of the remaining resources start listing up and when I further zoom out more all the resources listed up.

This is happening in all browers(edge, firefox, chrome) and is happening to everyone within the team. I have tried removing the cache, re logged in to the portal and all possible ways at client side, however somehow issue still persists.

Is there any ongoing issue with ARM api's which render everything on portal, which we are not aware of. Please assist.

Olga Os - MSFT 5,831 Reputation points Microsoft Employee

2021-04-05T23:38:40.863+00:00
@SARASWAT CHETAN Apologies for delay in response and all the inconvenience caused because of the issue. I couldn't find any reports about ongoing issues with ARM api's which render everything on portal.

I have few questions there. Kindly help me to scope down the issue.

Do you still have the same issue as you outlined above?

Did the Azure Portal worked before as expecting?

Is your team using the same network? Could you test from any different?

Do you see any errors in the browser console?

PS: If you are going to create the ticket, we recommend you first capture a browser trace and some additional information. You could find these steps here.
SARASWAT CHETAN 91 Reputation points

2021-04-06T04:47:38.773+00:00

Issue still persists. Below is the output from the console.
Olga Os - MSFT 5,831 Reputation points Microsoft Employee

2021-04-06T16:54:24.09+00:00

Thank you!

Could you please copy and past the session id + share the whole path there you navigate?
Like
SARASWAT CHETAN 91 Reputation points

2021-04-06T18:33:34.813+00:00

I have created a Service Request TrackingID#2104060060002179. Looks like an issue related to Ajax calls not rendering the inner resources pane within the resource group completely. In all 3 browsers there is a different error in console.

Firefox:

Edge:

Do you want the subscription id or the session id. From above snapshot it looks like subscription id, however below is the active session id from Console as requested:

f64bc47b2dea4cdf86f835616731b08d
Olga Os - MSFT 5,831 Reputation points Microsoft Employee

2021-04-06T20:08:55.147+00:00

Thank you @SARASWAT CHETAN . I could see your SR already taking care and you have PaaS dev engineer investigating the logs. I'll follow up internally to see how I can help them.
Sorry again for your experience while using the Azure Portal.
SARASWAT CHETAN 91 Reputation points

2021-04-08T12:44:51.777+00:00

Hi,
Any updates on this. Issue got resolved yesterday by itself and suddenly started appearing today again.
ssinsk 6 Reputation points

2021-04-09T01:07:31.93+00:00

Hello @SARASWAT CHETAN ,
I am sorry to hear this issue reoccurred in all browsers today again.
I just wanted to follow up with you and let you know that our support engineer is still investigating the issues you reported.
Thank you for your patience while we work through this.
Olga
Olga Os - MSFT 5,831 Reputation points Microsoft Employee

2021-04-19T18:23:37.067+00:00

Hey @SARASWAT CHETAN ,
Please kindly confirm if the same issue reoccurred during the last week.
Sincerely,
Olga
SARASWAT CHETAN 91 Reputation points

2021-04-19T18:36:30.47+00:00

Hi Olga,

Issue didn't occurred since last week . Currently the browser is reflecting Version: 7.204.0.5 for the azure portal(can be visible using Ctrl+Alt+D).

Will update if it occurs again. Support team had requested me to monitor the version as such on timely basis and also compare the pageVersion via fetching the portaldiagnostics.json file (using Ctrl+Alt+A)
Olga Os - MSFT 5,831 Reputation points Microsoft Employee

2021-04-19T19:16:47.02+00:00

Yes! I saw your conversation with our engineer. Glad to hear this issue didn't occurred since the last week.