Hi All, I personally never had to set the consent URL in my local experiments with Azure storage (and Polaris worked fine).
Cheers, Dmitri. On Thu, Apr 16, 2026 at 11:14 AM Jean-Baptiste Onofré <[email protected]> wrote: > Hi Nandor > > That's related to Azure AD afair. I remember (when I tested it) to use > local az CLI to get the values: > --tenant-id Your Azure Active Directory tenant ID. Find it in the Azure > Portal under Azure Active Directory → Overview → Tenant ID (a UUID like > xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). > --multi-tenant-app-name The display name of the App Registration you > created for Polaris to use when accessing Azure Storage. Find it in Azure > Active Directory → App Registrations → [your app] → Display name. > --consent-url Construct it manually using your app's client ID: > > https://login.microsoftonline.com/{tenant-id}/adminconsent?client_id={app-client-id} > > I hope it helps. > > Regards > JB > > On Thu, Apr 16, 2026 at 4:29 PM Nándor Kollár <[email protected]> wrote: > > > Hi All, > > > > A question about Azure storage integration came up recently on Slack. > While > > reviewing the Azure catalog section in the Polaris public documentation > > [1], we noticed a required consent-url parameter. Does anyone know what > its > > purpose is? Where can we find the value of this parameter? > > > > I checked the codebase, but aside from the CLI and the documentation, I > > couldn’t find any references to it. Would it be possible to remove it? > > > > [1] > > > > > https://polaris.apache.org/releases/1.3.0/getting-started/creating-a-catalog/catalog-azure/ > > > > Thanks, > > Nandor > > >
