New Outlook for Mac Version Released

I wish they would not call it Outlook. It incorrectly sets users' expectation. Especially Windows switchers.

Thanks @chriscollins for the link and thanks @talkingmoose for the blog entry.

Honestly, after reading that, this new version actually sounds like a serious step backward as far as functionality. There's far more missing in this release than anything they added in. I can't even really find anything of value to look to with this release. Maybe that it now uses mail headers for sorting/grouping instead of the subject line? That's nice I guess, but honestly it doesn't even come close to justifying all the stuff they left out. The UI was updated, but like mentioned above, that's only lipstick on a pig, not to mention its just a repurposed look from the Windows and web clients anyway.
I guess MS is bent on ruining Outlook on the Mac in their wasted effort to make Windows seem like the better platform. Same ol' Microsoft. I had hopes that with with the recent helm change, things would also change with development, but I guess not. We ask for more and they give us less.

I wish they'd offer some preference that you could force it to only work 'online' and forget the stupid huge local database.

My only hope is that since this is early release clearly targeted towards 365 users since you can't get it any other way that the left out missing features are potentially going to make their way back in before a release to on-premises customers.

WELL, it looks like the process name for the new Outlook installer (downloaded from portal.microsoft.com with a 365 account) is simply "Installer". That is going to make it hard for us to block it...

@dgreening What's the process for the app? Isn't that what you want to block?

Both Outlook 2011 and Outlook 2015 share the same process name of "Microsoft Outlook", so that is a no-go.

I would prefer to block the install process instead of letting them install it and then saying "No you can't run this".

I don't have it, but I'm assuming the process name for the app would just be "Microsoft Outlook". If so, adding that as a restricted item would end up blocking legit installs, so I can understand why he would want to block just the installer.

Is the installer an app bundle? If so, maybe in this one case you can try putting in the app bundle name and not the executable? If its just a package installer, then you may be out of luck with blocking it. I have never found any good way to block those.

It looks like a regular installer package to me...

Then forget it. Unless you're oK with blocking any and all installations done by the client, you can't block those. At least not without some built in config profile method like with the OS X Yosemite beta that Apple released.
You may want to see if you can block access to any web address for the installation package so users can't download it at all. Not sure if that's even viable.

Anyone know where the log files are saved when you turn on "logging for troubleshooting"? Outlook 2011 saved them to the desktop, but it appears that 15 saves them somewhere else.

Just an FYI. The local data is located here:
~/Library/Group Containers/UBF8T346G9.Office
Logging should be there as well under OfficeLogging...

I'm in the Outlook TAP program so probably can't say much more...
Can confirm this, the released version on O365 requires an O365 account to activate.
I haven't been a fan of Outlook - but for what it is, it is MUCH better than 2011. All the appropriate enhancement request s are getting requested.

Yea I'm not sure it's a good idea to delete an entire container for any one issue...but...seems like that's what the Microsoft "community" is saying is a fix for an unrelated issue:

Large Log files in ~/Library/Group Containers
http://answers.microsoft.com/en-us/office/forum/office_onenote-onenote_mac/large-log-files-in-librarygroup-containers/8c8cdaaf-9b4d-4a05-855f-97967048cb9b