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.

Desired functionality:

• Open a blank document in MS Word.


• Save it as "MyTempReport.docx"


• MS Word menu > Insert [tab] > Text [group] > Quick Parts > Field ...


• From "Field Names" choose "FileName".


• In the Field Options area there should be an additional checkbox described as something like File basename only (without ".docx" file extension ).


• With the option selected the resulting field will be "MyTempReport".

Motivation: In MS Word you sometimes want to insert a FileName field in the header or footer but make it independent of the fact that the document source is a Word document. This is the case when you want to distribute the Word document saved as a PDF. It no longer remains true that folk receiving PDFs from you are receiving a "MyTempReport.docx".

when sharing links to documents, etc, the URL's are way too long.

Can you integrate something like bitly or another tool to make them less than the 208 characters that the last link I shared was.

The ideal place to offer this feature is when you are given the option to 'copy' the URL.

I am also waiting to see a response from this post: https://goo.gl/h6wTRt

The last comment says:
*Update March 15, 2016: We’re working on a new approach to shortening the sharing links that will better enhance our users’ experience. Unfortunately, we had to remove the current experience in preparation for the new one. We always keep the best interest of our users in mind so we appreciate your patience as we work this out. We expect to have it ready soon.

As we build solutions in Office 365, we often need the concept of service accounts, but there's no mechanism for this - other than setting up a fake user account. It's quite common to need an identity that isn't tied to a specific person, not unlike what we typically do on premises.

The idea would be that these service accounts could have the restriction that they wouldn't have a login, so they would have no mailbox, no OneDrive etc., but could be secured like any other AD principal.

Here are some example uses for this type of account:
* As the identity under which a Flow or PowerApps would run. This would mean that the service account could have the least required permissions to create the necessary connectors within Office 365, but the identity would make more sense for actions like sending emails.
* In PowerApps, using a service account to do something or reach into content sources in a certain way that cannot depend on the current user's credentials. For example, reaching into HR's site for a particular list of information curated specifically for the request or user which would be displayed on a form.

Additionally, these service accounts should not incur licensing charges, since they wouldn't be used by any actual person. Currently, we end up creating fake users (maybe Firstname: HR, Lastname: Administrator) and paying the monthly licensing charge for them.

Finally, having these service accounts would greatly improve the solutions outside consultants can provide in Office 365. It rarely makes sense to see an email coming from a consultant or a list item created by a consultant who used to work in the tenant or to have that consultant's identity tied to any solution. In Flow, we can make individual Flows into Team Flows, but the consultant identity is still stuck in the owners list. Some sort of service account would decouple the person creating the solution and the identity running it.