Hello @KT!
I understand you need Cross Tenant Access for your solution
Yes you can achieve this by using Azure Private Link, which provides a private endpoint in your virtual network, enabling direct access to Azure services over a private connection. You'll need to ensure that private endpoints are configured and that public network access is restricted to your logical server. For SQL databases that reside in a different tenant, you might need to use SQL authentication or a service principal in the tenant where the SQL database is located. Managed Identities (MI) are not currently supported across different tenants for Azure SQL access
https://learn.microsoft.com/en-us/azure/azure-sql/database/private-endpoint-overview?view=azuresql
The error message you're seeing suggests there's an issue with token-based authentication.
you're trying to access resources across tenants, you might need to invite a user from the other tenant as a guest and assign the necessary permissions using Azure's IAM (Identity and Access Management). This doesn't require a Shared Access Signature (SAS) or shared access keys if the user is invited as a guest. Once the user from your tenant is granted access as a guest in the customer's tenant, you should be able to create an indexer without needing to whitelist IP addresses
I hope this helps!
The answer or portions of it may have been assisted by AI Source: ChatGPT Subscription
Kindly mark the answer as Accepted and Upvote in case it helped!
Regards