<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
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D54z00006rpkSLCAYOkta Classic EngineOkta Integration NetworkAnswered2022-03-09T20:39:40.000Z2021-03-08T04:01:28.000Z2021-03-11T10:47:52.000Z

JesseB.86765 (Customer) asked a question.

March 8, 2021 at 4:01 AM
O365 User Provisioning when domain is not in O365

I am trying to auto provision users in O365 from Okta. We are a Gsuite shop, so for O365 we use the .onmicrosoft.com for usernames. When I try to provision a user, I am getting an error stating "Could not create user Kuntz in Office 365, received error: 400 Invalid syntax. Parameter Name: USERPRINCIPALNAME."

 

I am using custom user creation, and just trying to pull in okta user lastname to create the user.

  • 3 answers
  • 654 views

  • SathishK.23283 (Customer)

    Are you using OKTA only for the User provisioning ?

    Because if you are using the default domain i.e your onmicrosoft.com for SSO -WsFed, that will not be federated.

    • JesseB.86765 (Customer)

      If possible, I'd like to use primarily for provisioning, if I can't use for SSO, I suppose we could just use SWA for office apps.

  • SathishK.23283 (Customer)

    I dont this without federation its possible to enable provisioning alone. Even I tried thh same and am getting the identical error.

This question is closed.
Loading
O365 User Provisioning when domain is not in O365