You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: microsoft-365/enterprise/manage-multitenant-org-settings.md
+20-4Lines changed: 20 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,6 +73,22 @@ To manage free/busy calendar sharing for tenants in your MTO:
73
73
74
74
The calendar sharing feature for MTO utilizes [Organization relationships in Exchange Online](/exchange/sharing/organization-relationships/organization-relationships). The organization relationship will share all users calendar availability and must also be set up by the other tenants in your MTO for free/busy information to be shared.
75
75
76
+
#### Troubleshoot calendar sharing issues
77
+
78
+
There are a couple of reasons that calendar sharing enablement might not work as it should:
79
+
80
+
1. "Failed to edit or create an organization relationship with [tenant]. Please try again later"
81
+
82
+
1. This error typically only requires a refresh after some time. If error persists, review the setting in [Exchange Online](https://admin.exchange.microsoft.com/#/organizationsharing) to see if there is an existing organization relationship with this tenant.
83
+
84
+
1. "Failed to get all domain names for [tenant]. This is an issue with how [tenant] has their primary domain name configured."
85
+
86
+
1. This error typically requires the partner [tenant] to manage the status of their default domain here: [https://admin.microsoft.com/#/Domains](https://admin.microsoft.com/#/Domains). Additional details regarding domain troubleshooting can be found here: [Manage domains ](/microsoft-365/admin/get-help-with-domains/find-and-fix-issues)
87
+
88
+
1. "Failed to create a new organization relationship with [tenant]. This could be due to a duplicate organization relationship."
89
+
90
+
1. Review existing organization relationships in [Exchange Online](https://admin.exchange.microsoft.com/#/organizationsharing) to see if one already exists with this tenant. If organization relationship already exists with [tenant], review settings to ensure it is set up as desired.
91
+
76
92
## Set up MTO user labels in Teams for tenants in your MTO
77
93
78
94
MTO group admins can now configure an optional label for each tenant that will be displayed alongside MTO synced user's display name in Teams. This allows MTO synced users to be distinguishable within the MTO in Teams interactions.
@@ -110,7 +126,7 @@ To manage MTO user labels for tenants in your MTO:
110
126
> [!NOTE]
111
127
> This is currently only available for private preview.
112
128
113
-
Admins can opt-in for MTO notifications to ensure they don’t miss any updates or changes to their MTO. Receive email notifications regarding any updates to the MTO such as: a new tenant joined the MTO, a tenant left the MTO, an MTO setting changed (user labels, owner/member role, MTO name), or user sync status changed (Must have full-mesh sync set up via M365 admin center). Email notifications are sent weekly, as long as any updates were made to the MTO. No notification will be sent if nothing has changed.
129
+
Admins can opt-in for MTO notifications to ensure they don’t miss any updates or changes to their MTO. Receive email notifications regarding any updates to the MTO such as: a new tenant joined the MTO, a tenant left the MTO, an MTO setting changed (user labels, owner/member role, MTO name), or user sync status changed (Must have full-mesh sync set up via M365 admin center). Email notifications are sent daily, as long as any updates were made to the MTO. No notification is sent if nothing has changed.
114
130
115
131
Additionally, in the MAC MTO portal you can review the updates and see any Microsoft recommended actions. Opt-in and select the user(s) in your org who you would like to receive the notifications.
116
132
@@ -139,12 +155,12 @@ These permissions are required to fetch cross-tenant synchronization details and
0 commit comments