I support a client who maintains several contact groups within Outlook. Her work flow previously involved sending these groups to her coworkers and other people outside her company as an attachment in Outlook. Since switching to Outlook 2016 / Office 365, the attached Outlook Groups are blank when opened up by someone not on their Office 365 domain. Pay day 2 steam for mac. Can you confirm this is how Outlook 2016 / Office 365 is supposed to work? Are there any work arounds? If this were just about email routing, I'd set up distribution groups for them. However, there seems to be a lot of tweaking of the groups once they are received.

When new email arrives in Gmail account, forward email with attachments to Office 365 Outlook. Use this template It's free to get started. Last September, we announced new capabilities in Office 365 Message Encryption that enable users to seamlessly collaborate on protected emails with anyone. This release included Do Not Forward an out-of-the-box policy that encrypts emails and Office attachments, and restricts the content and email from being forwarded, printed or copied.

What work-arounds are there that would allow her to send a contact group to users outside their domain, and for those users to quickly/easily import the group back into Outlook? I think I found a work around. As stated above, when forwarding the Outlook contact group from a 365 account, the attachment is a link to the object in 365, and doesn't contain the actual list of contacts in the group. This is why the attachment appears blank when viewed by someone outside the same 365 domain (it's a link to an object they can't see). HOWEVER, if I add an account outside that 365 domain to Outlook (a Gmail account, in my case), attach the Outlook group to a message, but send the message from the non-365 account, the attachment will contain the actual Outlook group with all the contact information. I was thinking that MS had intentionally disabled this functionality for 365, but considering the way the work-around handles things, I'm not so sure anymore. I think it's a legitimate bug.

I think I found a work around. As stated above, when forwarding the Outlook contact group from a 365 account, the attachment is a link to the object in 365, and doesn't contain the actual list of contacts in the group.

This is why the attachment appears blank when viewed by someone outside the same 365 domain (it's a link to an object they can't see). HOWEVER, if I add an account outside that 365 domain to Outlook (a Gmail account, in my case), attach the Outlook group to a message, but send the message from the non-365 account, the attachment will contain the actual Outlook group with all the contact information. I was thinking that MS had intentionally disabled this functionality for 365, but considering the way the work-around handles things, I'm not so sure anymore.

I think it's a legitimate bug.

Receiver 11.9.15 for Mac. Release Date: Apr 3, 2015. High performance web and self-services access to virtual apps and desktops. Enables use of multiple monitors without the need to disable 'Displays have separate Spaces'. Simplified Citrix Viewer. Improved logging. Citrix receiver for mac earlier version download.

Hi, I'm having a rather odd problem with my Outlook for Mac 2016 on O365 E3. I cant open attachments in random emails in my Inbox. I can see the email has an attachment but its greyed out and I cant open it. I can see and open the attachment via OWA, on my Tablet and on my phone but not on Outlook for Mac 2016.

There are a few emails with the same issue and it is NOT specific to a sender or an attachment type. The only thing I can recall is having a few syn errors when I had a problem with my Internet but my Sync error logs are now empty. Hi, What's the build number of your Outlook for Mac client?

Does this issue happen to other users in your organization? Do you have any other email account type configured in your Outlook? Does this issue happen to other email accounts? When this issue happens, please try forwarding the email to yourself to see if the issue persists. We can also try forwarding the emails to another email account to check the result. Regards, Steve Fan TechNet Community Support Please mark the reply as an answer if you find it is helpful.