Skip to main content

Email one-time passcode (OTP) - Enable guest users without federation or registration

By

Nowadays, if you use Azure to run your business, there is an 80% chance of using Azure AD as the Identity and Access Management system. The strong integration with on-premises AD tenants, Google, Facebook and Azure AD B2B and Azure AD B2C makes our life much easier. 

What if you provide access to an external user that cannot be authenticated using AD, MSA (Microsoft Account) or social identity providers? Or you don't know what kind of IAM the user has.

OTP (Email one-time passcode) is your friend in this situation. The feature enables us to share resources or provide access to external users without requesting them to create an account. The only thing that the user needs is an email address and nothing more.

The one-time passcode is sent to their email address at the moment in time when they want to access the resource that you shared with them. The passcode is valid for 30 minutes and provides a valid session for the next 24 hours. If the passcode or session expires, there is no problem because the external user can request a new passcode again.


It's a great way to share resources with external users, especially when there is no federation or integration with their IAM system. The external user is added as guest to your Azure AD, and they are subject to Azure AD access policies (e.g. MFA) and can be managed directly by you. 

When OTP is active, there is a small trick. When you share a resource with an external user, you don't know if OTP will be used or not. The OTP is used if the user:

  • Don't have an MSA (Microsoft) account
  • Don't have an Azure AD account
  • No federation configured with their tenant
Because of this, when a user already used OTP and later gets an MSA, Azure AD or Ferederated account, they will still use OTP. From Azure AD, you will need to reset their redemption status to allow them to use another method. 

The excellent integration with OneDrive and SharePoint enables us to use OTP to share content with Guest users. Why? Because OneDrive and SharePoint are using Azure AD, the OTP is fully integrated (as long as your IT allows OTP (big smile).


Why you should use OPT (Email one-time passcode)?

A simple way to share content and provide access to your organization to external users that are not part of your tenant or a federated tenant. The access control it is fully managed by your organization and audited. Who, what and when can access is fully managed by IAM, as you would managed a guest user.  

Because of this, OTP can be used with success to share notes and materials after a meeting with external attendees. 



Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...
Post a Comment
Read more