Forum Discussion
Connecting to Australian-hosted Smartsheet data
Hi MattB-Motive
We understand your concern. With AU-hosted Smartsheet, the connection works differently because it’s considered a separate regional instance, so native connectors aren’t applicable.
You’ll need to use the AU-specific API endpoint and token, since there’s no cross-region connectivity between AU and US/EU environments. Most setups use the REST API instead of the standard connector.
For Power Automate, the HTTP action works with the AU endpoint, but it’s generally used for simpler cases.
Here are some community threads where API-based solutions have been implemented:
Solved: Connecting Multiple Smartsheets - Microsoft Fabric Community
Solved: Connect Smartsheet Resource Management API to PBI - Microsoft Fabric Community
I hope this clarifies the situation. If I’ve misunderstood any part of your situation, please let us know.
Regards,
Microsoft Fabric Community Support Team.
Hi MattB-Motive
Yes, you completely hit the nail on the head—the native Power BI and Power Automate Smartsheet connectors are hardcoded to the US and EU data islands, which leaves the Australian region completely stranded. Because the AU instance is a strictly isolated environment with its own localized infrastructure, standard OAuth authentication loops fail, and you have to bypass the built-in connectors entirely. The absolute cleanest, zero-cost way to handle this in Power BI is to bypass the Smartsheet option entirely and use the native Web connector in Power Query to hit the official AU API endpoint at https://api.smartsheet.au/2.0/. You will need to generate a Personal Access Token (PAT) from directly inside your AU Smartsheet account settings and pass it explicitly via an authorization header within your Web.Contents M code—ensuring you use split RelativePath syntax rather than string concatenation so the Power BI Service doesn't drop the credentials during a cloud refresh. If you are using Power Automate, you will hit the exact same barrier with the standard flow actions, so the proven workaround there is to utilize the premium HTTP action block to manually construct your GET or POST requests directly against the api.smartsheet.au endpoint, using your token in the headers field. The biggest hidden gotchas you will encounter with this setup are that tokens generated in the US or EU environments will not work for the AU instance, data cannot be shared across different regional boundaries, and you may need to configure an On-premises Data Gateway or explicitly check the "Skip test connection" toggle in the Service dataset credentials pane to get the web-based API queries to authenticate seamlessly on a schedule.