Hey Bubble Community! 
Following up on our massive V2.0 update (which fixed the dreaded “Text too long” enterprise error), I realized something important: Bubble’s native “Signup/login with a social network” action is just too limiting for modern apps. So… I completely removed it. 
Starting with this latest update, the native Bubble OAuth flow is officially retired. Everything is now handled by the custom “Microsoft Entra Login Element”.
Whether your users are logging in with Personal Accounts (Outlook/Hotmail) or Enterprise/Education Accounts (Entra ID / Office 365), this single powerful visual element handles it all seamlessly.
Here is why this completely changes the game for your apps:
1. True Dynamic Scopes (No More Scary Consent Screens!)
With the old native login, you had to ask for all permissions upfront. If you wanted to read a user’s calendar, you had to ask for it on day one, which scared users away. Now, scopes are 100% dynamic! You can trigger the login element and ask for basic info (User.Read) to get them into the app. Later, when they click a “Sync Calendar” button, you can trigger the element again asking for Calendars.Read. Better user experience = higher conversion rates! 
2. One Element to Rule Them All
No more separate setups for Personal vs. Business accounts. The MSAL.js element automatically detects the account type and authenticates them securely.
3. The New “Passwordless” Bubble Login Workflow
Because we are bypassing Bubble’s native system to give you unlimited token sizes, we use a brilliant “Magic Link” workaround to log the user into your Bubble database instantly without them ever knowing.
Here is the exact workflow you should build with the new element:
Because we are bypassing Bubble’s native system to give you unlimited token sizes (fixing the “Text too long” error), we don’t save passwords. Once the user authenticates via the Microsoft pop-up, you must log them into your Bubble database.
Choose one of the two passwordless workflows below:
Option A: The Direct Login Method (Recommended for seamless UX)
This method uses a clever “temporary password” workaround to instantly log the user in without them leaving the page.
1. The Trigger:
When Button Login is clicked
Add action: Trigger Microsoft Login (Define your scopes, e.g., openid profile email User.Read).
2. The Login Event:
- Create a new workflow event:
When a Microsoft Entra Login User Logged In.
3. Action 1: Auto-Provision New Users
-
Add action: Account > Sign the user up.
-
Email: This MicrosoftEntraLogin's Email
-
Password: Calculate formula > Generate random string (e.g., 12 characters).
-
Only when: Do a search for Users (Email = This MicrosoftEntraLogin's Email):count is 0 (This creates the account and logs them in if it’s their first time).
4. Action 2: Generate Password for Returning Users
-
Add action: Account > Assign a temp password to a user.
-
Email: This MicrosoftEntraLogin's Email
-
Only when: Do a search for Users (Email = This MicrosoftEntraLogin's Email):count > 0
5. Action 3: Log Returning Users In
-
Add action: Account > Log the user in.
-
Email: This MicrosoftEntraLogin's Email
-
Password: Result of step 2 (Assign a temp password)
-
Only when: Do a search for Users (Email = This MicrosoftEntraLogin's Email):count > 0
6. Action 4: Redirect
- Add action: Navigation > Go to page (e.g., Dashboard).
Option B: The Secure Email Magic Link Method
If you prefer strict verification, you can force the user to click a magic link sent to their Microsoft email inbox.
1. The Trigger:
When Button Login is clicked
Add action: Trigger Microsoft Login.
2. The Login Event:
- Create a new workflow event:
When a Microsoft Entra Login User Logged In.
3. Action 1: Auto-Provision New Users
- Add action: Account > Sign the user up (Use the exact same setup as Step 3 in Option A).
4. Action 2: Send the Magic Link
-
Add action: Account > Assign a magic login link.
-
Email: This MicrosoftEntraLogin's Email
-
Just create link, don’t send email:
UNCHECKED (Bubble requires this to be unchecked to successfully send the link for front-end workflows).
-
Navigate on login: Choose your destination page (e.g., Dashboard).
5. Action 3: Show a Notification
- Add an alert or text to your page: “Success! Please check your Microsoft email inbox and click the magic link to enter the app.”
Making API Calls (Fetching Data)
Now that your user is securely logged in, you can fetch their Microsoft data (Profile, Photo, Groups, etc.) without hitting database limits!
-
In your workflow or dynamic text, select Get data from an external API.
-
Choose one of our pre-configured calls (e.g., Microsoft Login - Get My Groups).
-
The Bubble editor will prompt you for an access_token.
-
Pass the token directly from the visual element’s memory: This Microsoft Entra Login's Access Token.Go check out the updated plugin and let me know if you love the new Dynamic Scopes as much as I do!
Happy Building! 