Bug 41257 – create contact objects in azure for use with office365 Mail (Exchange Online)

Bug 41257 - create contact objects in azure for use with office365 Mail (Exchange Online)


Summary:	create contact objects in azure for use with office365 Mail (Exchange Online)

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Office 365
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Mail maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-05-11 14:23 CEST by Daniel Tröder
Modified:	2019-01-03 07:22 CET (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Feature Request
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Daniel Tröder

2016-05-11 14:23:41 CEST

The LDAP attributes 'mailAlternativeAddress' and 'mail' (contacts) are mapped to Azure Users 'otherMails' attribute. But that data is not used by the Office 365 Mail app. It probably uses 'Contact' objects (https://msdn.microsoft.com/en-us/library/azure/ad/graph/api/entity-and-complex-type-reference#ContactEntity).

Modify the listener in such a way, that contact data is synchronized to the Azure objects that are used by the Office 365 apps like 'Mail'.

Comment 1 Daniel Tröder

2016-05-24 16:04:49 CEST

When implemented, contact Alice. Having used a o365 API, we can try to become a MS partner.

Comment 2 Stefan Gohmann

2019-01-03 07:22:56 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.