RedApple Freight
Azure AD (Microsoft Entra ID) Setup Guide
App Registration for Single Sign-On (SSO) Integration with Base44
Prepared ForIT / Infrastructure Team
ApplicationRedApple Freight Logistics Platform
DateOctober 2025
Purpose: This guide walks your IT team through registering an application in Microsoft Azure (Entra ID) so that RedApple Freight's logistics platform can authenticate users via your company's Office 365 / Microsoft accounts. Once complete, please send back the three highlighted values (Client ID, Client Secret, and Tenant ID) so the Base44 configuration can be finalized.
!Prerequisites
- Access to the Azure Portal (portal.azure.com) with sufficient permissions to register applications (Application Administrator or Global Administrator role).
- Your organization's Microsoft 365 / Entra ID tenant must be active.
- Estimated time: 10-15 minutes.
1Register a New Application in Azure
- Sign in to the Azure Portal at https://portal.azure.com using an admin account.
- In the left navigation menu, search for and select Microsoft Entra ID (formerly "Azure Active Directory").
- From the left menu under Entra ID, select App registrations, then click + New registration at the top.
- Fill in the registration form:
- Name:
RedApple Freight SSO (or any name your team prefers) - Supported account types: Select "Accounts in this organizational directory only" — this restricts sign-in to your company's tenant.
- Under Redirect URI:
- Select platform: Web
- Enter the following URL exactly as shown below:
Redirect URI (copy exactly)https://app.base44.com/api/apps/6a286f502f02a0584a44e6bb/auth/sso/callback
Important: The redirect URI must match exactly. A mismatch will cause authentication to fail.
- Click Register to create the application.
2Configure API Permissions
- After registration, you'll be taken to the app's overview page. In the left menu, click API permissions.
- You should see Microsoft Graph permissions. Verify the following delegated permissions are present (they are usually added by default):
| Permission | Type | Purpose |
|---|
| openid | Delegated | Enables OpenID Connect authentication |
| email | Delegated | Allows the app to read the user's email address |
| profile | Delegated | Allows the app to read the user's basic profile |
| User.Read | Delegated | Allows the app to read the signed-in user's profile |
If any of the above are missing, click + Add a permission → Microsoft Graph → Delegated permissions → search and add the missing ones, then click Add permissions.
Note: These are all delegated permissions (not application permissions), so no admin consent grant is required beyond the initial user sign-in. However, if your tenant requires admin consent for all apps, click Grant admin consent for [Your Tenant] at the top of the permissions page.
3Create a Client Secret
- In the left menu, click Certificates & secrets.
- Under the Client secrets tab, click + New client secret.
- Enter a description (e.g.,
Base44 SSO) and choose an expiration period:- Recommended: 12 or 24 months (your organization's policy may dictate this).
- Click Add.
Copy the secret value immediately. The Value column is only visible once, right after creation. If you navigate away, you will not be able to retrieve it and will need to create a new secret. Do NOT copy the "Secret ID" — copy the Value.
4Collect the Three Required Values
After completing the steps above, please collect and send back the following three values. These are needed to finalize the SSO configuration in Base44.
Values to Send Back
1. Application (Client) IDFound on the app's Overview page
2. Client Secret ValueFrom Certificates & Secrets (the Value, not the Secret ID)
3. Directory (Tenant) IDFound on the app's Overview page
Where to find them: Go to the app registration → Overview page. You'll see Application (client) ID and Directory (tenant) ID near the top. The Client Secret Value is on the Certificates & secrets page (visible only once after creation).
5Optional: Token Configuration (Recommended)
- In the left menu, click Token configuration.
- Click + Add optional claim.
- Select ID token type.
- Check email and upn (user principal name) to ensure the email claim is always included in the token.
- Click Add, then Save.
Why this matters: RedApple Freight maps authenticated users to their existing accounts by email address. Including the email claim ensures the mapping works reliably for all users in your tenant.
!Security Notes for Your IT Team
- The Client Secret is a sensitive credential. Please transmit it securely (not via plain email). Consider using an encrypted channel or password-protected document.
- When the client secret expires (per the expiration you set), a new one must be created and shared so the SSO integration can be updated. We recommend setting a calendar reminder.
- The redirect URI is specific to this application. If the Base44 app is ever recreated or migrated, the URI will need to be updated in Azure.
- Only users within your Entra ID tenant will be able to sign in (assuming "Accounts in this organizational directory only" was selected). External/guest users will not have access unless the account type is changed.
!What Happens Next
- Your IT team sends back the Client ID, Client Secret Value, and Tenant ID.
- The Base44 administrator enters these values in the app's Authentication settings and enables SSO.
- A "Sign in with Microsoft" button will appear on the RedApple Freight login screen.
- Users sign in with their Office 365 credentials and are mapped to their existing RedApple Freight accounts by email address.
Questions? If your IT team has questions about the Azure configuration, they can refer to Microsoft's official documentation:
Register an application with the Microsoft identity platform.