Disabling Group Policy from Office 365 Business users doesn't make a lot of sense to me. A lot of smaller- to medium-sized businesses which have an IT point person who does more than just IT, rely on tools like Group Policy to keep their users running cleanly and uniformly. While larger enterprises use Group Policy to eliminate having to perform the same customization on thousands of devices, small business use the same thing, not to save time managing thousands of devices, but to centralize efforts and increase efficiency when resources are scarce. I was disappointed to learn that all of my GPOs from before 365 are now entirely invalidated, especially after "joining up" in full and subscribing to Office 365, and after migrating from our on-prem. Exchange server to Exchange Online. It feels like a bit of a slap in the face, actually.

We have great trouble as we have "Poland" as our country in our organisation-profile and the VAT of our partner-companya in poland, and we can´t change that to "Germany" and to our VAT-No.
This should be possible what we see. A company could move to another country and so it should be possible to change a country and VAT for future (!) invoices.
Support tells me that the only actual way is to setup a new organization with our country, buy (!) the same stuff that we already have, backup anything localy in the old organization (wow, this means the whole Office365, Sharepoint and Azure stuff..., in a running organisation), and copy them to the new organization. I don´t see that we can do this, even if we get a refund for our already paid stuff.
Please have an indeed look what´s a realistic scenario for that.
We´re talking also about 2 EU-countries.
THANKS

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.

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.