@Amar-Azure-Practice There is no way to find the client application IP which is consuming the message as this is PI information and this information is not logged at our end. Any client passing the right credential can send/recive the messages and service bus never know what was the client/application that send/recive the messages.
The best way would be regenerate your primary/secondary connection string of your namespace level so the request will become invalid for the client consuming the messages. If you have any shared access policy at your entity level then you can also regenerate both the keys as your client may also use these keys to authenticate the request. Please alos verify if there is any Azure role-based access control (RBAC) at your namespace level which might be used for fine-grained control over a client’s access to resources.