Mimecast API integrations create new workspaces

[sapg]

Describe the bug
The Mimecast integrations from the content hub create new workspaces when you follow the instructions provided. I've seen a workaround for this problem on one of he closed tickets on this subject but that workaround isn't practical for me as I will be deploying these connectors multiple time for multiple instances of Mimecast.

To Reproduce
Steps to reproduce the behavior:

1. Go to Sentinel ==> content hub
2. Search for Mimecast, choose one of them,
3. Follow the setup instructions
4. After hitting the deploy button, observe new LA and Sentinel workspaces with the same name as the function app.

Expected behavior
The connector should use the workspace that is specified during setup.

Additional context
See the two closed tickets where the title starts with, "Mimecast API integration"

[github-actions]

Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.

[v-sudkharat]

Hi @sapg, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates by 30-11-2023. Thanks!

[v-sudkharat]

Hi @sapg, I hope this message finds you well. This solution's is a supported with Mimecast, we kindly request you to raise an issue ticket with Mimecast's support team.
Sharing the Mimecast mail ID and support link -
Mail Id - "support@mimecast.com"
Link - "https://community.mimecast.com/s/contactsupport"
So, closing this issue. If you still need support for this issue, feel free to re-open it any time. Thank you for your co-operation.

Thanks!