You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I encountered the following error when connecting to China Azure Redis using AAD:
var configurationOptions = ConfigurationOptions.Parse($"{cacheHostName}:6380").ConfigureForAzureWithServicePrincipalAsync(clientId!, principalId!, tenantId!, secret!).GetAwaiter().GetResult();
AADSTS90002: Tenant 'xxxxxxxxxxxxxxxxx' not found. Check to make sure you have the correct tenant ID and are signing into the correct cloud. Check with your subscription administrator, this may happen if there are no active subscriptions for the tenant.
Trace ID: ff96b70b-5f00-496a-80e4-7ab7c0f38500
Correlation ID: db509495-a670-47fe-ab16-65b43808a328
Timestamp: 2023-08-30 03:14:04Z
It seems that there is no endpoint specified to connect to China AAD. How can we specify this parameter?
The text was updated successfully, but these errors were encountered:
That's great. When will the next SDK version be released? Because this feature has already been previewed on the Azure portal in China. There may be many customers who want to use this feature.
I encountered the following error when connecting to China Azure Redis using AAD:
var configurationOptions = ConfigurationOptions.Parse($"{cacheHostName}:6380").ConfigureForAzureWithServicePrincipalAsync(clientId!, principalId!, tenantId!, secret!).GetAwaiter().GetResult();
AADSTS90002: Tenant 'xxxxxxxxxxxxxxxxx' not found. Check to make sure you have the correct tenant ID and are signing into the correct cloud. Check with your subscription administrator, this may happen if there are no active subscriptions for the tenant.
Trace ID: ff96b70b-5f00-496a-80e4-7ab7c0f38500
Correlation ID: db509495-a670-47fe-ab16-65b43808a328
Timestamp: 2023-08-30 03:14:04Z
It seems that there is no endpoint specified to connect to China AAD. How can we specify this parameter?
The text was updated successfully, but these errors were encountered: