Issue in Service with axis not aligning

[ThomasNorth]

Hi there,

I am using the line and clustered bar chart visual.

I have set the axis for both y and secondary to be 0 min and 200 max

In desktop this works ok:

In service, the Secondary Y axis is now showing higher (slightly). As you can see the 200 value on the secondary y axis is about 5/ 10 % higher than the 200 on the Y axis

Was fine until last week. Note, its not in all tenancys. One working ok still in service, another one this issue is appearing so appears to be a recent deployment to the service

[v-tsaipranay]

Hi @ThomasNorth ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

[v-tsaipranay · Accepted solution]

Hi @ThomasNorth ,

Thank you for reaching out to the Microsoft Fabric Community Forum. Thank you @rohit1991 for your response.

Yes, this is a recent Power BI Service regression. The difference between tenants is expected due to the phased rollout of Service updates, which explains why it worked previously and still works in another tenant.

There is no published ETA for when this will be corrected. The fix will apply automatically once your tenant receives the updated Service build.

Thank you.

[ThomasNorth]

Thank you for your support. We will wait until the fix is applied

[rohit1991]

Hii @ThomasNorth 

It's a Power BI Service rendering bug. The line & clustered column chart currently ignores the exact min/max sync between primary and secondary Y-axes in some Service builds, even when both are explicitly set (e.g., 0–200). That’s why it looks correct in Desktop but slightly misaligned in Service, and why it varies by tenant (staggered rollout). There’s no reliable fix at report level right now; the only workarounds are to avoid dual Y-axes, use separate visuals, or wait for the Service update to be corrected.

[ThomasNorth]

Ok thank you. Is this a recent issue? It worked fine until last week, and still works ok in another tenant. Is there a known date for the service update to be corrected?