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

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.

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.

To whom it may concern:

My name is Sherry Masih and I work as a project manager for HH Builders. We are a construction development company located in New York. Last Year we migrated all our emails to Microsoft office 365 in the lieu of using the Microsoft Project Task sync option to Outlook. Since we are a construction company it is very necessary for us to be able to assign tasks to each project manager in Microsoft Project and have it directly synced with their Outlook Tasks. This feature has tremendously worked well with our organization from the time we implemented it. We have not had any issues with this feature and almost all of our employees are using this feature to get their tasks sync’d with outlook and phones.

However I was told today that Microsoft will be deleting this feature from office 365 and we will no longer have access to this. I would like to tell you that this feature was the only reason why we switched over to office 365 and we have spent a lot of money and hours training our employees to use this feature correctly. We absolutely need this feature and I need to talk to someone who can help me understand better how I can replicate this feature.

I would appreciate if someone would get back to me about this.

Thank you
212-924-3100

I have several users that over the last 1-2 months increasingly have experienced that their Outlook wont sync. All of them then experience as message in the bottom of the Outlook screen that says "Need password", but if you click it, you just get a quick blink of a white screen, and then it disappears.

While the issue is present for the users, it is not possible for them to create a new Outlook profile, as it wouldn't connect to the mailbox. I had luck with just rebooting my own computer, that fixed the issue for me, but only until the next day. Other users had bigger problems getting it to work.

The issue apparently seems to be an implementation on "Web Account Manager" (WAM) in Office/Windows. The solution is to set below registry key to 1 in below path.

Path: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity
Key: DisableADALatopWAMOverride (DWORD)

There is a bit more information on the error on below links. As said, the issue is resolved with above registry fix, but it obviously isn't optimal, and preferably it would be fixed by a software patch, either for Windows or Office.

https://support.microsoft.com/en-us/help/4025962/you-can-t-sign-in-after-you-update-to-office-2016-build-16-0-7967-or-a
https://www.reddit.com/r/Office365/comments/7kklt2/autodiscover_issue_on_outlook_2016_o365_exchange/
https://community.spiceworks.com/topic/2025536-outlook-2016-365-keeps-asking-for-credentials?page=3

Looking at the modified values in Site Contents has always been a quick way to recognize where activity has occurred - if it has. Without running any code we can quickly see if a site has been used recently. (It was easier to eyeball this in SharePoint 2007 in the vertical listing than it is in SharePoint 2013+, but that's a different UI issue - tiles aren't helpful for every use case.)

For months now, a list no one has touched for over a year might say "Modified 23 hours ago". It seems as though lists and libraries are being "touched" by some background process, changing the modified time incorrectly.

An example would be the site in my Sympraxis Office 365 tenant at https://sympraxis.sharepoint.com/sites/Demos2013/_layouts/15/viewlsts.aspx

On that page, I see a number of lists and libraries that say "Modified 9 days ago" or "Modified 10 days ago". I know for a fact that I have not modified any of those lists or libraries in quite a long time (at least months) and I'm the only person who would be in there. I'm attaching a screenshot showing this.

I've seen this in multiple tenants on Office 365, so it isn't just something in my tenant. It's VERY confusing to end users and brings into question the integrity of the platform.

I've been told by support that this is "expected"behavior" and has been the case since SharePoint 2013. I believe this should be fixed.

I've also submitted this to sharepoint.uservoice.com at https://sharepoint.uservoice.com/forums/329214-sites-and-collaboration/suggestions/15112005-modified-dates-in-site-contents-should-reflect-con. Please vote early and often!