Ability to create Shared Calendars (companywide) that require no end-user configuration (Outlook 2016, OWA, and mobile) AND only includes that, a Shared Calendar.

I can think of 4 different methods to create a companywide Shared Calendar: Shared Mailboxes, SharePoint, Exchange Public Folders, and Office 365 Groups. However, these methods have huge drawbacks which I will explain below based on Shared Calendars.

Shared Mailbox
Pros:
- Automatically added to Outlook 2016
- Shows up under Calendar tab as a separate calendar without user intervention.
Cons:
- Adds an extra mailbox and cannot be disabled.
- Adds an extra contacts folder and cannot be disabled.
- Must be added manually to OWA.
- Does not integrate with mobile devices (I tested this with Outlook for Android).

SharePoint
Pros:
- Only creates the calendar.
Cons:
- Managing is way too much work; add and remove users, create, etc.
- Requires user to go to SharePoint site to sync with Outlook 2016.
- Must be added manually to OWA.
- Does not integrate with mobile devices (I tested this with Outlook for Android).

Exchange Public Folder
Pros:
- Only creates the calendar.
- Once added as Favorite in Outlook 2016, it automatically gets added to OWA (I think, could be wrong).
Cons:
- Way too many steps to create the first calendar.
- User must add calendar as “Favorite” to make it useful.
- Favorites in Outlook are a nightmare.
- Does not integrate with mobile devices (I tested this with Outlook for Android).

Office 365 Groups – Not subscribed:
Note: Subscribed method is just non-sense. You cannot tell what appoint was created in your calendar or the groups’.
Pros:
- Has an APP to use in mobile devices.
- Automatically added to OWA.
- Ease to create and manage.
- The way it adds the shared mailbox is elegant (Subfolder within primary mailbox).
Cons:
- Requires a separate APP to see calendar which only has Agenda view…
- Adds an extra mailbox and cannot be disabled.
- User must add group as “Favorite” to see calendar.

The perfect Basic Shared Calendar:
1) Creates only a Shared Calendar (no mailbox, no contacts folder, etc.).
2) Ability to add members from Office 365 portal, Outlook 2016 and OWA (At least).
3) Shared Calendar is an independent calendar and DOES NOT overwrite member’s calendar.
4) Automatically gets added to members’ Outlook 2016, OWA, and Outlook for Android/iOS/Windows Phone.

The above would be great for Contacts.

I'm surprised this is still a thing, but if you populate the mobile phone attribute for users in AD, you apparently can (though not in my experience) get said attribute to sync to your Azure AD profile. However, it DOES NOT sync to your SharePoint online/Delve profiles.

This is a fairly annoying thing that's been on people's radar for about 3 years, apparently. I found a powershell script that is supposed to get around the issue, but so far I haven't gotten it to work.

Having that attribute be one of the ones that syncs from Azure AD profiles would be very helpful. Even better would be the ability to map attributes like you can in SharePoint On-premises.

Within an Office 365 Group document library (SPO site), the ‘Shared With’ column does not reflect current state of sharing status.

Here are some examples:
1. When you remove a user’s permission from an item in a Group the ‘Shared With’ column still shows that it is shared with that user.
2. When you copy a file in a Group the ‘Shared With’ column retains the original users listed even though it is no longer shared with them.

Acknowledge this is by design:
https://support.microsoft.com/en-sg/help/2987770/the-shared-with-column-displays-users-who-no-longer-have-access-to-a-document-in-sharepoint-online

Feedback from our users is that this is not an intuitive user experience. Ideally the ‘Shared With’ column should only display current state of an item's permissions, not what has occurred in the past. To be clear: if I have shared an item with Bob and then remove Bob's permissions from the item the ‘Shared With’ column should not display Bob's name. It is very confusing to users to see that Bob is listed in the ‘Shared With’ column but he doesn't have access when you dive deeper.

In addition to this the user experience in removing permissions reverts back to the old SharePoint permission UI. Ideally this should be similar if not perfectly aligned to how OD4B does permissions on items.

What we want to see changed:

1. ‘Shared With’ column to only show current state of item's permissions
2. Permission removal/adjustment UI to be aligned with OD4B (able to be adjusted in details pane). We don't want to go to 'ADVANCED' to adjust the permissions.

In an Office 365 Group calendar you can create a new meeting invite and uncheck the ‘send an invitation to the group’ check box. As expected, this will stop anyone in the group receiving the invite notification.

However, if you need to make any updates to that event (it doesn’t matter what update you make) and click save, a notification will be sent to all members in the group. In addition to this, the Group will also add the calendar event to the personal calendar of the individual who has made the update.

This is not an intuitive user experience.

Three parts to this proposed solution:

1. Change the experience to ensure that the calendar event respects the initial setup upon creation i.e. if the ‘send an invitation to the group’ check box is unchecked, remain this way even if the event is updated and don't send notifications.

2. When adding additional members to the event ensure the ‘send an invitation to the group’ check box is not greyed out and we can make the choice to check or uncheck.

3. Furthermore, can the ‘send an invitation to the group’ be unchecked by default.

People in the world, both admins and users, are constantly asking whether new features Microsoft has announced as on the way or rolling out are deployed to their tenant yet. This often results in a lot of confusion and probably support cases and questions into Microsoft asking these types of questions.

We could solve this by building some sort of "Is this feature deployed to my tenant yet?" tool. This tool would very simply authenticate the person checking via Azure Active Directory, and then return a simple result for the feature you are checking on. Results could be:

- Yes
- Targeted Release Only
- No

It would also be nice if IT Admins could provide a small bit of text/guidance for users in case they come across a feature where the answer is Yes, but the user does not have access. This could point them towards some sort of Support function, request process, etc so IT has a better idea of the needs of their users.