How to access table storage from Managed API, both are under same subscription.

To access Azure Table Storage from a Managed API (like Azure Functions or Azure App Service) under the same subscription, you can use Azure Managed Identities to secure the access. Here's an outline of how to do it:

Step 1. Enable and Obtain the Managed Identity

1. In the Azure portal, go to your API's resource blade (for example, the Azure Functions or App Service blade).
2. Under the settings section, click on "Identity."
3. Under the "System assigned" tab, switch the Status to "On" and save your changes.
4. After the identity has been created, note down the "Object ID" as you will need it in the next step.

Step 2. Grant Access to the Table Storage

1. In the Azure portal, navigate to your Table Storage account.
2. Under "Access control (IAM)", click "+ Add" and select "Add role assignment."
3. In the "Add role assignment" panel, select the "Storage Blob Data Contributor" role. This role allows for read, write, and delete access to blob data (including tables).
4. In the "Select" field, paste the "Object ID" you obtained in the previous step. It should resolve to the name of your API.
5. Click "Save" to add the role assignment.

Step 3. Access the Table Storage from the Managed API

In your API, you can now use the Azure SDK to access your Table Storage without explicitly providing any connection strings. Azure will automatically use the Managed Identity to authenticate your requests.

If you're using C# and the Azure.Storage.Tables library, it could look something like this:

csharpCopy code
var client = new TableServiceClient(new Uri("<your-table-storage-url>"), new DefaultAzureCredential());

The DefaultAzureCredential() class automatically handles the authentication using Managed Identities if they are available.

Please replace "<your-table-storage-url>" with the URL of your Azure Table Storage service. You can find this in the Azure portal under the "Properties" section of your Table Storage account.

Please note that this approach requires that your API is running in Azure, as Managed Identities are not available when running locally. For local development, you can use your own credentials or a connection string, but make sure not to commit these to your code repository.

Thanks!