#Tableau Cloud85 人がディスカッション中

I have implemented the solution for day and week. Check the updated workbook attached.

@Prasanth Prabhakaran

Option 1: If you are using AWS, you can use Private Connect (it has a fixed cost, and also a per consumption cost) 

Option 2: The second option is that your database should be allowed from the Tableau Cloud Ips: 

Option 3: Use Tableau Bridge. Basically the Bridge Clients need access to the internet and to your databases.  An interesting approach is described here:

Unfortunatelly, there is not an inbuilt option to configure VPN or Proxy in Tableau Cloud. 

If this post resolves the question, would you be so kind to "Accept this Answer"?. This will help other users find the same answer/resolution and help community keep track of answered questions. Thank you. 

Regards, 

Diego Martinez 

Tableau Visionary and Tableau Ambassador 

Hi, 

I hadn’t heard back from you after my previous reply — is it alright to consider that earlier question resolved? 

If so, please close the previous thread (mark it as the Accepted Answer), and I’ll continue supporting you. 

https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000jAN1c0AG

Looking at your current requirements, it seems that when a date is selected, a list of dates should appear, and the latest date should already be selected. In this setup, will the date be a single‑select field? 

Hi Kiran,

This looks like an Azure AD (Entra ID) OAuth refresh token issue, not a config mistake on your end. 

Why:

Tableau doesn't yet support single-use/rotating refresh tokens for Azure/Entra ID OAuth connections. If your tenant enforces token rotation (via Conditional Access, sign-in frequency, or CAE), Tableau's stored refresh token gets invalidated quickly — so scheduled refreshes fail even though a manual connection test succeeds (the test can trigger a fresh token; the stored one for scheduled runs can't). 

Desktop works vs. Cloud fails:

Desktop re-authenticates interactively each time. Cloud relies on a stored token for unattended scheduled runs — if that token's been rotated out, it breaks. 

Check these:

1. Azure AD Conditional Access — sign-in frequency, CAE, or refresh token rotation on this app registration
2. Whether a dedicated OAuth client is registered for Tableau in Azure AD (vs. the default shared one) — recommended for scheduled refreshes
3. Re-save credentials directly on the data source's Edit Connection page, not just Account Settings
4. Consider a service account instead of a personal identity — less exposed to MFA/session policies
5. Does it fail immediately or after a set time? A short window points strongly to a Conditional Access session policy

Fastest next step: check Settings → OAuth Clients in Tableau Cloud to see if a dedicated Azure AD client is set up.

@Himal Singh

Unfortunately, there is no way to do everything. 

There is an embedded license optimized for public sites, but you’ll need to set it up as a separate site from your existing Tableau Cloud site, and you’ll have to manually copy your existing workbooks and data sources. 

Please refer to the URL below. 

@Patricio Milan

That's really odd, you should check if the user maybe has a forwarding rule for his email, or a spam filter or something similar related to his account. 

Also, you may create a support case, thus Tableau support can take a look of the logs, and check if there is a problem from the Tableau side or maybe they can send the email with the reset link from another account to the user. 

If this post resolves the question, would you be so kind to "Accept this Answer"?. This will help other users find the same answer/resolution and help community keep track of answered questions. Thank you. 

Regards, 

Diego Martinez 

Tableau Visionary and Tableau Ambassador 

Hi @Umesh Chorge

dealing with WebEditing and credentials can be a bit unstable. I've seen a lot of instances over the years were credentials for some mysterious reasons were not committed or using old ones or using credentials from another tenants while the Analysts were working daily on multiples tenants.  

This is one example: 

As you seem to work with embedded data source directly in the workbook, as Diego said in his earlier post, use published data sources. To keep your datasource stable and modify your workbook content irrelevant of Athena connections even in WebEdit. 

And ideally you modify your published data sources using Tableau Desktop if you can.