Hello,

I am familiar with using a plus sign following my email alias to create dynamic unique addresses for a Gmail account. e.g. test.email+signedup@gmail.com will arrive at my Gmail mailbox, where I can then apply rules based on the 'To:' address. See this page for details: https://support.google.com/mail/answer/22370

I tested this on my Office 365 address and it works, but only for email addresses in my parent domain. Using the aliases on subdomain addresses results in a 'recipient not found' NDR.

Does anyone out there have more information on this feature or if it even is one for 365 / Exchange?

Thanks!
Ryan

As organisations grow, or have to separate different business areas in different O365 tenants it would be useful to be able to share or federate global address lists between different tenants. The only current choices are:

1. Create contact objects in tenants which are then disconnected from the original user - this means if the user details change the contact in the other tenant becomes out of sync.




2. Where domain federation in in place and directory synchronisation services running for each tenant, create on premise AD users as mail enabled users and ensure each directory sync for each tenant looks at the other domains. This will ensure that user objects are sync'd to the other tenant as mail contacts.

The second method works quite well from a point of ensuring that user details are always accurate with AD objects but only works in an environment where domain federation and dirsync are used. This is not an option in a completely cloud based environment.

Allowing GAL federation/sync between tenants would reduce on premise administrative burden and also provide a solution for cloud only adoption.

Enable option to subscribe by email Office 365 Health Service Incidents and Advisories.

Global Admin or any Distribution list be able to receive the service health dashboard summary or any major service outage alerts over the email.
There has to be an option to subscribe to the alerts (old school SharePoint Lists alerts mechanism) providing an email. This functionality should be only permissible to Global Admin and can add up to 5 email addresses.
This will reduce the over head of an Admin to keep going back to dashboard to be able to monitor health, Or if this needs to be assigned to a separate team (without exposing the Admin Center).

Tenant administrators should have the ability to specify whether or not new features such as Teams, Sway, etc. are enabled by default within their tenants. Just like there's the ability to set a tenant to receive First Release, Admins should be able to specify how changes are introduced to their environment. It's great that there are Powershell commands to turn features on/off but it would be much easier to either set these new features to be off by default, or enable Admins to enable when organizations are ready to absorb those changes. Functionality like Teams is absolutely fantastic, but without the right change management planning it becomes confusing for users. For Tenant Admins that either ignore announcements of new features, or are unavailable to turn them off when they become available - this is an appropriate solution to enable organizations to effectively manage how they are consuming Office 365.

Every time there is some sort of notification in Office 365 Admin (i.e. your subscription expires in 57 days, you cancelled a subscription, etc.), all of the admins get a VERY annoying notification and "ding" noise every time they navigate to a new page in the Portal/SharePoint/etc. It makes it nearly impossible to work. First of all, these notifications are next to useless and some can't even be dismissed (i.e. you cancelled a subscription - who cares??). Second, you should be able to dismiss them easily or just turn off the functionality altogether. This was a bad feature update by Microsoft and has nearly driven all the admins in our office crazy.

I created an account for a client of mine. I set it up on my company (registered in Sweden) to be able to fix this smoothly for my customer. When I now want to change ownership to his company (registered in Switzerland) I cannot do that. That is strike one.

Ok, so I was told that I should setup a new account and then you could help me migrate all data to the new account, so I did. When I came back asking for the migration step I get the instructions to do this via exporting to pst-files. I MEAN COME ON!! What year is this?

Now my only hope is that I can use migrationwiz or something else to be able to migrate the data. All this because I cannot change the owner of an account.

So what is my proposal:
1. Either make it so that you are able to change ownership of an account (I think lots of SMBs out there would benefit from this) or,
2. Help the customers with the migration - should be much hassle for you guys.

That would be greatly appreciated!