Hello Bishnu Shankar
Greetings!
I understand that you want to connect to the Redis cache privately using a bastion host for multiple users simultaneously.
Could you please provide the following details to assist you with this issue:
- What type of Bastion SKU are you using? Note that the Developer SKU does not support concurrent users.
- How is the Redis Cache being accessed privately? Have you enabled any private endpoints for the Redis Cache?
- Are you using SSH to connect to the Redis cache?
Check the below document for more understanding:
And also check the Bastion SKU limitations:
Feature | Basic SKU | Standard SKU | Premium SKU |
---|---|---|---|
Connect to target VMs in same virtual network | Yes | Yes | Yes |
Connect to target VMs in same virtual network | Yes | Yes | Yes |
Connect to target VMs in peered virtual networks | Yes | Yes | Yes |
Support for concurrent connections | Yes | Yes | Yes |
Access Linux VM Private Keys in Azure Key Vault (AKV) | Yes | Yes | Yes |
Connect to Linux VM using SSH | Yes | Yes | Yes |
Connect to Windows VM using RDP | Yes | Yes | Yes |
Connect to Linux VM using RDP | No | Yes | Yes |
Connect to Windows VM using SSH | No | Yes | Yes |
Specify custom inbound port | No | Yes | Yes |
Connect to VMs using Azure CLI | No | Yes | Yes |
Host scaling | No | Yes | Yes |
Upload or download files | No | Yes | Yes |
Kerberos authentication | Yes | Yes | Yes |
Shareable link | No | Yes | Yes |
Connect to VMs via IP address | No | Yes | Yes |
VM audio output | Yes | Yes | Yes |
Disable copy/paste (web-based clients) | No | Yes | Yes |
Session recording | No | No | Yes |
Private-only deployment | No | No | Yes |
https://learn.microsoft.com/en-us/azure/bastion/configuration-settings#skus
If you have any other questions or are still running into more issues, let me know in the "comments" and I would be happy to help you.