201
Views
4
Comments
Solved
Microsoft Multi Factor Authentication

We aim to incorporate Microsoft Authenticator for user authentication during login, similar to how it works on Outlook and Teams. However, after researching, I couldn't find any Forge assets or implementations that align with our requirements. Could you provide any insights or resources that might assist in integrating this into our login process? 

2021-10-09 07-57-44
Stefan Weber
 
MVP
Solution

I have written a tutorial on how to use the Microsoft Login Connector Forge component to add SSO with AzureAD/Entra in applications. https://itnext.io/getting-started-with-outsystems-and-microsoft-graph-123006356d41.

Best

Stefan

UserImage.jpg
Cameron Knox

Thank you for sharing the tutorial link Stefan. We're currently dealing with a challenge regarding our OutSystems contract. To avoid exceeding our budget, we need to ensure that the implementation of the new feature doesn't create too many objects. Could you provide an estimate of how many objects this implementation might generate?

2021-10-09 07-57-44
Stefan Weber
 
MVP

The forge components have 14 application objects in total. I would say you can reduce that down by half if you modify the component.

If you want to implement an Entra ID Authorization Code Flow on your own you can check out my webinars here https://www.youtube.com/channel/UC-VrcqKzZYlhX6UsWj2DMDg

Just to note aside: Depending on your requirements I would say, that a custom login flow would consume 1 AO. That is either a callback screen, or a callback exposed REST API endpoint.

2025-12-09 14-11-18
Janakiraman JR

Hey Cameron Knox,

If you're looking to integrate Microsoft Authenticator for user authentication, it typically works hand-in-hand with Azure Active Directory (Azure AD). Here’s a quick rundown on how to get started:

  1. Head over to the Azure portal (portal.azure.com) and register your application under Azure Active Directory > App registrations. This step will give you an Application ID and allow you to configure authentication settings, including Microsoft Authenticator.

  2. In Azure AD, set up your application to use the appropriate authentication methods, which will include integrating Microsoft Authenticator.

Depending on whether you're working with a web app or mobile app:

  • For web apps, you can use Azure AD libraries like MSAL for .NET or MSAL.js for JavaScript. They handle OAuth 2.0 and OpenID Connect protocols seamlessly.

  • If it's a mobile app, go for Azure AD libraries tailored for iOS (MSAL for iOS) or Android (MSAL for Android).

When users log in, Azure AD will prompt them to approve the login using Microsoft Authenticator if multi-factor authentication (MFA) is required based on your policies.

While there might not be specific "Forge assets" for this integration, Azure AD and its SDKs cover a wide range of authentication scenarios, including those with Microsoft Authenticator. Dive into the Azure AD documentation and SDKs that match your app's platform to get started smoothly.

Hope this helps!

2021-10-09 07-57-44
Stefan Weber
 
MVP
Solution

I have written a tutorial on how to use the Microsoft Login Connector Forge component to add SSO with AzureAD/Entra in applications. https://itnext.io/getting-started-with-outsystems-and-microsoft-graph-123006356d41.

Best

Stefan

UserImage.jpg
Cameron Knox

Thank you for sharing the tutorial link Stefan. We're currently dealing with a challenge regarding our OutSystems contract. To avoid exceeding our budget, we need to ensure that the implementation of the new feature doesn't create too many objects. Could you provide an estimate of how many objects this implementation might generate?

2021-10-09 07-57-44
Stefan Weber
 
MVP

The forge components have 14 application objects in total. I would say you can reduce that down by half if you modify the component.

If you want to implement an Entra ID Authorization Code Flow on your own you can check out my webinars here https://www.youtube.com/channel/UC-VrcqKzZYlhX6UsWj2DMDg

Just to note aside: Depending on your requirements I would say, that a custom login flow would consume 1 AO. That is either a callback screen, or a callback exposed REST API endpoint.

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.