Connect to Custom Azure Applications/APIs
This guide covers authenticating with custom Azure Applications/APIs. You will need your Azure and PixieBrix Administrator to assist with the instructions in this guide.
Create/Register an Azure Application
📚 Azure documentation to Register an Application and Register an application with the Microsoft identity platform
Visit the Enterprise Applications page
Click New application

Click Create your own application

Provide a name for your application and click “Create”

Assign Users and Groups
Assign one or more users/groups to the application for them to access the application

Configure the Application Registration
Open the Application Registration for your application. To locate it from the Omnibar, search for the name and select the “Application” entry

Open the Authentication settings

Click “Add a platform”

Choose Single-page Application

Provide the following Custom Redirect URL. (The
[chromiumapp.org](<http://chromiumapp.org>)origin is a special origin that the Chrome Web Browser uses client OAuth2 flow redirects.)
Configure API Permissions
Select Manage > API Permissions

Add some base permissions. To allow sign in, select “Microsoft Graph” and choose the Open ID permissions:

Record the Application and Directory ID
Return to the Overview page for the application you created

Record the Application (client id) and Directory (tenant) ID for use with PixieBrix

Configure the PixieBrix Microsoft Azure Integration
To complete these steps for your team, you must be an Admin on your PixieBrix team. Alternatively, for development & testing, you may configure the integration in the Extension Console
From the Integrations section in the Admin or Extension Console, click the + Add Integration button in the top right corner.
To set up a cloud integration that your team can access, head to the Admin Console. (If you'd rather set up something locally, use the Extension Console. Learn more about Configuring Integrations.)
Search for and select the Microsoft Azure integration.
Provide the following information for the Application
Pushdown (read-only): the integration configuration will be pushed to your team members. They will each authenticate individually with the application
Application (client) ID: from the Application Registration Overview
Directory (tenant) ID: from the Application Registration Overview
Scope:
See the individual brick documentation (e.g. xxx and Lookup Microsoft Workbook Sheets)
You likely also want to set the offline_access scope, which will fetch a refresh token and reduce the number of times you need to re-authenticate
See the Microsoft Graph permissions reference for all available scope names

Testing the Integration Configuration in a Mod
Create a new Mod in the Page Editor, e.g., a Trigger
Add an HTTP Request Brick
Configure the brick:
Integration Configuration: select the Integration Configuration you configured in the previous section
Method: get

Run the Mod
Your browser will open the OAuth2 authentication flow
After you authenticate, the Output Panel will show your user’s profile information:

Last updated
Was this helpful?