<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z000076wryHCAQOkta Classic EngineLifecycle ManagementAnswered2025-03-19T09:00:28.000Z2021-08-12T07:30:55.000Z2021-08-18T07:55:24.000Z

xhmhk (xhmhk) asked a question.

O365 Provisioning - Login failed in task

Hello.

 

on a new O365 tenant, we enable the provisioning.

But when we want to push user to Office, we get a "login failed" error in the okta tasks.

Users are created in O365, but in cloud only mode.

 

The only solution I found for now is to disable the Azure Security Défault

https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/concept-fundamentals-security-defaults


  • Hello Francois,

     

    Thank you for posting!

    If you just set up your Office 365 tenant for the first time and have not yet added any custom domain, Office 365 will by default use the ‘.onmicrosoft.com’ domain, and users will be created with a UPN suffix of ‘@YourDomain.onmicrosoft.com’. Once you’ve added and verified a custom domain to Office 365, you can choose the default domain for your Office 365 tenant. That way, every time you create a new user account, it will automatically contain your custom domain’s UPN suffix (e.g., user@domain.com ). If you still having difficulties on setting up your new integration with Office 365 please open a support ticket.

    Expand Post
  • xhmhk (xhmhk)

    Hello Bangu.

     

    Thank for your reply, but it's not the reason of my message.

    There is an issue with the provisioning with Okta, using O365 credentials. The only solution so far to fix it, is to disable the Azure Security Default.

     

    Best regards.

    Expand Post
This question is closed.
Loading
O365 Provisioning - Login failed in task