Right now you have an "autosave" toggle on the Excel header. But this is set to "off" and is not able to be toggled on, unless you are working with a file on one drive. How presumptuous of MSFT - you put a control on the interface with no way to address it. And, your support is clueless (initially) as to why this is usable. Because they have all been trained to think that everyone uses everything you create all the time.

Or organization, like so many others, relies on Dropbox. I also use iCloud. And Box. And OneDrive. But my corporate standard is Dropbox. In preferences the autosave is turned on, BUT. IT. DOES. NOT. WORK. Lost both excel spreadsheets and powerpoint changes where I expected that the autosave would help me. Apparently, you don't have a very large test matrix.

You should only make features visible if the right back end was enabled. How can you let users think they are both protected (autosave clicked in preferences) and also NOT protected (toggle is unable to be clicked in product UI)?

This is a horrendous user interface mess. Please fix.

Autosave does not work correctly -- autosaved versions are corrupt
and no warnings are issued
(A) Make autosave work correctly
(B) Issue some warning online that it is not working correctly
(C) Existing online help from Microsoft does not even tell you the
correct folder where the autosaved files reside -- causes
big waste of user time trying to diagnose problem

Excel for mac 2011 Version 14.6.9
OS X El Capitan 10.11.6 (15G1004)

The correct folder in which files are autosaved:
/Users/username/Library/Application Support/Microsoft/Office/Office 2011 AutoRecovery
(Online help from Microsoft is totally wrong on this, as are suggestions
on many online forums.
Microsoft phone help also totally wrong, until the agent does 5-10
minutes of internal checking around and comes back with a
correction.)

Autosaved versions of an open xls file with new changes appear just fine in the correct folder. You can wach it happen. But every one of
these autosaved files is corrupt. The files are useless.

After 30 minutes online with an agent, finally get to "This is a known
problem with this version of Office for Mac and we are working on it.
Sorry!"

I understand the need to do conventional saves, and Excel does remind you of this in some help screens.

Nonetheless! Autosave is a longstanding feature of Excel, and there should be some iota of hope that it actually works!

And a call to help should be able elicit "it does not work and we're trying to fix it" in something under a half hour!

And a slightly more prominent warning would be nice. (Like when you set the autosave time interval!)

Also, please fix. Both the bug, and the substandard online and phone help.

I love the NumPad.

Who doesn’t? It’s the fastest way to enter numbers. It’s even been used to support specialised input methods.

But I’m not loving the numerical keypad on Excel 2016.

I currently use a Chinese Input software called Q9, which uses the 9 number keys on the NumPad as a method to input Chinese. On Excel 2016 for Mac, every time I hit a number key on the NumPad, Excel interprets it as me entering a number, even though I am just trying to use the NumPad to interact with my input software.

European users are experiencing a different but related problem. Users who previously used the NumPad decimal point key to produce a comma can no longer do so. No matter how they change the settings, if they press the decimal point key, it will produce a decimal point – even if they really want to produce a comma.

I think what is happening is that Excel is directly taking input from the numeric keypad and mapping it to a set of default values, disregarding any special rules which may be defined elsewhere.

This is hurting users of the NumPad.

Please fix this problem. I want to love the NumPad forever.

For reference:
I tried the same thing on Office 2016 for Mac. I did not get the same problem.
I am using Mac OS X Yosemite.

Possibly related issues:
http://answers.microsoft.com/en-us/mac/forum/macoffice2016-macexcel/how-to-turn-the-dot-key-into-a-comma/82458acd-0bdd-4b82-917f-940f969604ac
http://www.excelforum.com/excel-general/1100081-how-to-change-the-decimal-point-on-the-numeric-keypad-to-a-comma.html
https://excel.uservoice.com/forums/304933-excel-for-mac/suggestions/11107107-usb-numeric-keypad

https://support.office.com/article/upgrade-your-macos-to-access-new-office-365-for-mac-features-f6efc6b6-90f8-4e69-82dd-d0de32a111aa

There is some indication that Office for Mac 2019 will only support the latest current release of macOS plus the previous operating system. This is a formal request from an Enterprise admin to have Microsoft provide support for the current macOS operating system plus the two previous operating systems.

Apple has been absolutely horrendous in documenting and providing the appropriate management tools to deal with major restrictions they've been adding to macOS. This makes it much more difficult to deploy the latest macOS release on day 1. As an example, the majority of our users are still on macOS 10.12 and we are just getting to deploy macOS 10.13 (almost a year later). And that's not for lack of trying or testing.

Although the documentation for Excel in Office360 for Mac is quite good, it could be improved.

Windows and Mac advice should not be mixed: It's confusing.

Breaking up each topic into bite-sized chunks is great, but the chucks seem to wander away to a series of links to other topics.

There should be a terse summary for each function/action etc. in one statement because links tend to be distracting and lead to rabbit holes that lead to ... any number of topics. Links have been found to be less effective for learning than a narrative in one place.

Excel is wonderfully/horribly complex! Links are one way to spoon-feed documentation, but not necessarily the only way.

Another way would be to condense the docs by using a gentle modification of BNF (Backus-Naur Form: See Wikipedia for details).

BNF is a way of explaining all possible correct statements of a (computer) language by making the syntax of the language explicit.

As an Excel user already understands a great many concepts, the docs do not have to define every term down to the atomic level.

Excel already has a great way of presenting parameters of functions in a dynamic manner. This should stand.

However, users seeking the right function to achieve a goal are presented with a full-text narrative describing each function.

This is much longer/harder to understand than an abbreviated summary expressed in an easily understood formal 'documentation language'.

A documentation language would be somewhere between BNF and natural language.

Each term used would be defined (or assumed to be common knowledge). From this, valid combinations of terms (or sentences) could be defined and named etc.

All of this based on the concept that all ideas can be expressed in a few words or a short phrase. A perfect example of this is E=mc^2. All of mathematics is based on the same principle.

Anyone who has taken notes at a lecture is applying to natural language the ideas that are expressed here.

Documentation of Excel would be far more useful if, in addition to the docs already in use, a terse description of all the conventions and functionality in Excel were available.

This is, of course, all up to the authors of Excel and its documentation.