Receiving client.text_client_status_default when trying to log into VM via Bastion

Question

Receiving client.text_client_status_default when trying to log into VM via Bastion

Thompson, Elonna 35

I am receiving client.text_client_status_default error when I try to log into VMs via Bastion. This is only affecting me. Other people can log into the VMs just fine. I have tried different browsers, different laptops (same network though). private/incognito windows, on and off VPN...all with the same error. I've tried logging into multiple VMs using credentials from LCS.

2025-10-15_13-43-19

I feel like this is a network issue maybe? But do not know where to start to try to figure it out. I was connecting fine a few days ago.

Any input is appreciated.

Thank you.

Thompson, Elonna 35 Reputation points

2025-10-16T11:53:09.6066667+00:00

Deleted
Thompson, Elonna 35 Reputation points

2025-10-16T11:54:58.0966667+00:00

deleted
Stephen Lafferty 15 Reputation points

2025-10-16T13:30:51.51+00:00

Hello. I am seeing the same exact issue. Did you find a solution?
Thompson, Elonna 35 Reputation points

2025-10-16T13:32:27.6866667+00:00

@Stephen Lafferty Not yet Please let me know if you find solution.
Thompson, Elonna 35 Reputation points

2025-10-16T15:56:09.3033333+00:00

@Jeevan Shanigarapu

I have done most of these steps.

Here is the console log at the point I get the error:

This seems to have started when I had to change my MS ID password. I have changed it again to see if that corrected the issue, but it did not.
Brian Ketchledge 0 Reputation points

2025-10-16T17:19:27.7266667+00:00

Hello, I am seeing the same issue as well. Any solution?
Thompson, Elonna 35 Reputation points

2025-10-16T17:33:25.8333333+00:00

@Brian Ketchledge Not yet, if we find one, I will post it here.
Macheledt, Doug 5 Reputation points

2025-10-16T17:49:38.8833333+00:00

@Jeevan Shanigarapu I work with Elonna, I can login to azure portal with my credentials from her computer and connect to the VM's with Bastion so this doesn't appear to be a network, DNS, or browser issue with her system but something more with her account. It also appears there are a couple other users that have posted the same issue. Is there a know issue on the Microsoft side that could be causing this? Do you have any other suggestions?
Macheledt, Doug 5 Reputation points

2025-10-17T13:13:49.6033333+00:00

@Stephen Lafferty Thanks for this suggestion. I did this for Elonna's account and it seemed to resolve the issue for us also.
Thompson, Elonna 35 Reputation points

2025-10-17T13:13:55.22+00:00

@Stephen Lafferty Thank you so much, that seems to have worked for me as well.
Thompson, Elonna 35 Reputation points

2025-10-17T13:15:19.5366667+00:00

@Brian Ketchledge if you haven't resolved this on your side, try Stephen's suggestion.

Answer accepted by question author

1 additional answer

Your answer

Thompson, Elonna 35 Reputation points

2025-10-16T11:53:09.6066667+00:00

Deleted
Thompson, Elonna 35 Reputation points

2025-10-16T11:54:58.0966667+00:00

deleted
Stephen Lafferty 15 Reputation points

2025-10-16T13:30:51.51+00:00

Hello. I am seeing the same exact issue. Did you find a solution?
Thompson, Elonna 35 Reputation points

2025-10-16T13:32:27.6866667+00:00

@Stephen Lafferty Not yet Please let me know if you find solution.
Thompson, Elonna 35 Reputation points

2025-10-16T15:56:09.3033333+00:00

@Jeevan Shanigarapu

I have done most of these steps.

Here is the console log at the point I get the error:

This seems to have started when I had to change my MS ID password. I have changed it again to see if that corrected the issue, but it did not.
Brian Ketchledge 0 Reputation points

2025-10-16T17:19:27.7266667+00:00

Hello, I am seeing the same issue as well. Any solution?
Thompson, Elonna 35 Reputation points

2025-10-16T17:33:25.8333333+00:00

@Brian Ketchledge Not yet, if we find one, I will post it here.
Macheledt, Doug 5 Reputation points

2025-10-16T17:49:38.8833333+00:00

@Jeevan Shanigarapu I work with Elonna, I can login to azure portal with my credentials from her computer and connect to the VM's with Bastion so this doesn't appear to be a network, DNS, or browser issue with her system but something more with her account. It also appears there are a couple other users that have posted the same issue. Is there a know issue on the Microsoft side that could be causing this? Do you have any other suggestions?
Macheledt, Doug 5 Reputation points

2025-10-17T13:13:49.6033333+00:00

@Stephen Lafferty Thanks for this suggestion. I did this for Elonna's account and it seemed to resolve the issue for us also.
Thompson, Elonna 35 Reputation points

2025-10-17T13:13:55.22+00:00

@Stephen Lafferty Thank you so much, that seems to have worked for me as well.
Thompson, Elonna 35 Reputation points

2025-10-17T13:15:19.5366667+00:00

@Brian Ketchledge if you haven't resolved this on your side, try Stephen's suggestion.

Answer 1

Hello @Thompson, Elonna,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

We got a suggestion from one of the OP, The issue was resolved by following the below steps, we have requested to add the same IAM role, and after adding the IAM role, issue got mitigated.

"Assigned the Reader IAM role to a group of users for the server vnets" Since then, you can be able to connect to the servers via Bastion.**

Kindly let us know if the above helps or you need further assistance on this issue.**

Please do not forget to "Accept the answer” and “up-vote it” wherever the information provided helps you, this can be beneficial to other community members. It would be greatly appreciated and helpful to others.

Answer 2

Stephen Lafferty 15

@Thompson, Elonna This morning, I assigned the Reader IAM role to a group of users for the server vnets. Since then, we have been able to connect to the servers via Bastion. I am a bit puzzled though as this IAM role was never a requirement on the vnets. I wonder if there was a recent change on the Microsoft side. Wanted to pass this along in the event you are seeing the same.

Share via

Receiving client.text_client_status_default when trying to log into VM via Bastion

1 additional answer

Your answer