Cannot create Storage Container in National Cloud (China)

[TruongNguyen888]

• Package Name && Version:
  "@azure/arm-storage": "^16.1.0",
  "@azure/identity": "^1.5.0",
• Operating system:
• nodejs
  • version: v10.15.3
• browser
  • name/version: Firefox
• typescript
  • version: 4.2.3

Describe the bug
I am using the arm-storage package to create a new container in storage account via code. It works well for the azure global environment. Now i deployed my server into the china cloud and now it doesnt work any more.

To Reproduce
Here is the sample code to get the client in the china login:

const servicePrincipaleCred = new ClientSecretCredential(
    process.env.ARM_TENANT_ID,
    process.env.ARM_CLIENT_ID,
    process.env.ARM_CLIENT_SECRET,
    {
      authorityHost: process.env.NATIONALCLOUD?.toUpperCase() === 'GLOBAL' ? AzureAuthorityHosts.AzurePublicCloud : AzureAuthorityHosts.AzureChina
    }
  )

  const client = new StorageManagementClient(servicePrincipaleCred as any, process.env.ARM_SUBSCRIPTION_ID);

This works well.

Here is the code for creating the storage account:

client.blobContainers.create(
                            process.env.SA_RESOURCEGROUPNAME as string,
                            process.env.SA_ACCOUNTNAME as string,
                            newContainerName.toLowerCase(),
                            blobContainer
                        )

But now occurs this error:

Error: invalid_resource(status code 400). More details: AADSTS500011: The resource principal named https://management.azure.com was not found in the tenant named xxxx-xxxx-xxxx-xxxx-xxxx. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You might have sent your authentication request to the wrong tenant. Trace ID: xxxx-xxxx-xxxx-xxxx-xxxxCorrelation ID: xxxx-xxxx-xxxx-xxxx-xxxxTimestamp: 2021-07-30 16:30:44Z

So the problem is, i dont know where i can set up the Azure Resource Manager for China
("https://management.chinacloudapi.cn")

Can you help me maybe?
I hope this is the right place to question.

Greetings Truong Nguyen.

[ramya-rao-a]

Thanks for reporting @TruongNguyen888

Can you try passing the baseUri in the options when creating the client? I have updated your code to take this option below

const client = new StorageManagementClient(servicePrincipaleCred as any, process.env.ARM_SUBSCRIPTION_ID, {
   baseUri: "https://management.chinacloudapi.cn"
});

[ramya-rao-a]

@sadasant Am guessing this is going to be the same problem as #15945?

[sadasant]

@ramya-rao-a if it’s the same problem as #15945, setting the baseUri won’t help until we merge and release something similar to this PR: Azure/ms-rest-js#457

[TruongNguyen888]

@ramya-rao-a Thank you for your reply. I tried your suggestion but the same error occurs again

[ramya-rao-a]

Thanks for the confirmation @TruongNguyen888
Can you try the workaround mentioned in #15945 (comment) while we work on the solution for this issue?

[nickzhums]

@TruongNguyen888 thank you for the feedback. We as the product team are very interested in learning about your experience using the JavaScript SDK. Would you be interested in a quick 20-30 min call to talk about your thoughts? The time can be flexible, thanks!

[ramya-rao-a]

Hello @TruongNguyen888

The issue was in the package @azure/ms-rest-js which is a dependency of the @azure/arm-storage package you are using.
We have released a new version for @azure/ms-rest-js that should fix this issue.

Please ensure you have the latest version of this package and let us know if this is still a problem

[ghost]

Hi @TruongNguyen888. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “/unresolve” to remove the “issue-addressed” label and continue the conversation.

[ghost]

Hi @TruongNguyen888, since you haven’t asked that we “/unresolve” the issue, we’ll close this out. If you believe further discussion is needed, please add a comment “/unresolve” to reopen the issue.