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

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.

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.

We want to see if it is possible to make a global change (likely in exchange) so that when Rightpoint people book meetings, they are by default booked in 25 minute increments. In other words, the default meeting time would be 25 mins and they could increase it to 50 mins.

The business goal here is to:
Give people time to get from one meeting to the next by adding “walk time”
Avoid meeting overruns and therefore allow the next meeting in the same room to start on time
Challenge people to be more efficient with meeting time

We need a solution that will work on both PC and Macs.

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".

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.

Email Signatures are still saved and stored on a local machine and are different for each client. This requires the user to setup their signature separately on each of their devices. Signatures are one of the last custom settings that do not save back to the Exchange server. For example :Custom Rules, Custom Categories, Auto-Complete Contacts, etc. all save back to the exchange server. It seems like the next logical step to save signatures on the exchange server as well. In addition to not having to setup a signature every time a device is upgrade, this would also allow users to setup their signature once and have it be the same in Outlook, OWA and Outlook for iOS.

We need a feature to be able to turn off certain notifications to our alternate email address in Office 365.

As Office 365 administrators, we are require an alternate email address that is not part of your Office 365 tenant. In most cases that would be your personal email address that is not provided by your work. This makes sense for password resets if administrators forget their password to log into the tenant.

Along with password resets, we also receive Office 365 statements, changes to tenant subscriptions and other notifications. These should have an option to turn off since all of these are company work related. It does not make sense that work notifications are required to be sent to alternate personal email addresses of administrators. Business emails should stay with business email addresses, not personal email addresses.