<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
0D50Z00008G7UfLSAVOkta Classic EngineOkta Integration NetworkAnswered2025-03-30T09:04:21.000Z2018-04-09T11:51:10.000Z2019-06-07T13:46:10.000Z

ar9ss (ar9ss) asked a question.

Edited by varun.kavoori1.5210444522562532E12 September 5, 2018 at 1:19 AM
o365 email alias
Hi,

 

I've followd the guide for adding the proxyaddresses attribute, but am not seeing what should, presumably, be an additional field under the user profile. I note that we use User Sync, not Universal Sync (which does not appear to be an option for the O365 app). Is this necessary to utilise email aliases, and is this something that we need to pay more for?

 

Many Thanks,

 

Felix
  • 12 answers
  • 3.93K views

  • valentin.nitu1.4597812366904814E12 (Okta, Inc.)

    Hey Felix, the user sync provisioning type should provide the ProxyAddress attribute in the Office 365 schema. If you have followed our guide for adding the attribute you would also need to add the attribute from the schema and map it either from an Okta profile attribute or Active directory. If that value is not pulled from somewhere we will not push anything to Office. 

    The documentation that I`m reffering to: https://support.okta.com/help/Documentation/Knowledge_Article/Okta-Enhancements-with-Microsoft-Office-365-Integration-1961576155#ProxyAddresses

    If you require assistance within your setup I would recommend to raise a ticket with Okta support.
    Expand Post

  • ar9ss (ar9ss)

    Hi Valentin, thank you for the quick reply. We don't use AD - Okta is the source of truth. I can see the proxyaddresses attribute in the Microsoft Office 365 Attribute Mappings in the app,

    0EM0Z000000FNGn

    but no extra field appears under the user profile. I've added one manually in the Okta profile (is this the right approach?) called Email Alias,

    0EM0Z000000FNGs

    and this appears in the profile, but when I enter an address, it is not synced across to O365 (I entered this yesterday, and it still has not synced).

     

    Have I misunderstood how this works?

     

    Regards,

     

    Felix
    Expand Post

  • valentin.nitu1.4597812366904814E12 (Okta, Inc.)

    Hey Felix, our documentation starts from the premise that you use AD. The expression is built on it. 

    Try to map to the Office 365 ProxyAddress an Okta string array attribute (you will need to create a custom string array attribute). Add the values for proxyAddresses there but make sure the first one is the primary email address. Once you save the profile after update a push should be done to Office syncing the information.
    Expand Post

  • ar9ss (ar9ss)

    Hi Valentin,

     

    Many thanks for your help, but that goes way beyond my knowledge of Okta.

    I'll open a support case.

    It would be worthwhile having actual documentation for this scenario, with, perhaps, an example. As more and more tech refreshes attempt to rid themselves of AD, and use a SaaS-only IDAM, surely having guides which address the (after all simpler) approach of using Okta as the primary IDAM, would be in Okta's interest? Just a thought!

     

    Cheers,

     

    Felix
    Expand Post

  • 00u3zbqr2OhjHMYAm1t1.4704211223430703E12 (Customer)

    Felix,

     

    If support gave you a working custom string array for this, please reply in this thread as I'd like to accomplish the same thing.

     

    Cheers,

     

     

    Greg

    Expand Post

  • ym5kk (ym5kk)

    Hi Felix, did you manage to get it work in the end?

    I have the same Issue: no AD and need Alias in Office365.

     

    Thanks

  • 1ngtx (1ngtx)

    Hi Felix, another Okta admin here with the same issue. Were you able to find a solution?

  • BillJ.27066 (Customer)

    I have the same issue, too. I would love to find a solution to this because a have a few users that have alias email addresses and the initial setup of Okta provisioning to Office 365 wiped all of that out.

  • JavierT.77498 (Customer)

    Looks like there are a ton of us starting to make do without LDAP and running into these issues. Have not seen any great solution here for this type of item.

  • JavierT.77498 (Customer)

    To update this ticket, we are starting to see some success with the Ldap interface app under directory -> directory integrations. We are using this for Jamf and it looks like its working, we had to edit the path they suggest, but that seems to be working. Next we will test it with our O365 integration and I will let you guys know if that goes well.

10 of 12

Loading
o365 email alias