Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Vote for your favorite vizzies from the Power BI Dataviz World Championship submissions. Vote now!
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
Solved! Go to 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.
Hi @ThomasNorth,
Thanks for posting about this bug, it should be resolved in the next few days.
In the meantime, and for future reference, there is another way to sync your y1 and y2 axes.
1. Remove the min/max values from the y2 axis, so they are both Auto
2. Turn off the y2 axis values section (if it's already off, turn on then off again in some cases)
3. The bar and line should now both use the y1 axis
If you prefer to have both show, then this method won't work. The good news is we should have your chart as it was soon.
Respectfully,
Zoe Douglas (DataZoe)
Follow me on LinkedIn at https://www.linkedin.com/in/zoedouglas-data
See my reports and blog at https://www.datazoepowerbi.com/
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.
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.
Hi @rohit1991, do you know if there is any ETA yet on this fix it is still causing a challenge. Could you point me to where I can monitor/ know when this has been rectified? Thank you
Thank you for your support. We will wait until the fix is applied
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.
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?
Vote for your favorite vizzies from the Power BI World Championship submissions!
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 18 | |
| 10 | |
| 9 | |
| 8 | |
| 6 |
| User | Count |
|---|---|
| 47 | |
| 40 | |
| 39 | |
| 25 | |
| 24 |