Mayki5

I "had an interest in IT" for a few years, but really got started when the IT manager at a local primary took me on for a year as a volunteer and got hired on after that.

Are the SRV records you mentioned for purposes of Autodiscover? If Autodiscover CNAME and SRV records are both present in DNS, then Outlook typically fails to connect. I would recommend removing the SRV autodiscover if it is present. It'll be worth running the Microsoft Support and Recovery Assistant, as it'll run more comprehensive checks when trying to configure a new Outlook profile. https://support.office.com/en-gb/article/about-the-microsoft-support-and-recovery-assistant-e90bb691-c2a7-4697-a94f-88836856c72f

It would be worth checking Microsoft's documentation here: https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-office-3 @TechMonkey is using Option 1. The approach by @PlantHead is Option 2/3. Note that for Option 3, most Tenancies need to use *domain*.mail.protection.outlook.com now instead of *domain*.mail.eo.outlook.com. It'll be whatever Office 365 tells you the MX record for your domain should be.

I'm up for it for a bit of a change. Never really got in to it at the right time, so all my characters are relative newbies.

I think you were close with that, just need to change the -ne to -notcontains. That should then list everything where specifically the SendAs user is not present.

Those EOP licences are for scenarios where you want to use Office 365's filtering for On-Prem mailboxes, where all of your email is delivered to Office 365 first.

@Koldov For OVS licences it is correct that it's not a qualifiyng purchase. However, Pro Plus on OVS entitles you to the Pro Plus on Office 365 for no cost anyway. Your licencing partner should be able to assist the two are linked, and then just assign the licence from Office 365 to the user's account.

For the Office Apps, it looks for a licence directly on your Office 365 account. If you have Pro Plus on OVS it would only count if your OVS is linked to Office 365, and you've assigned the licence that way.

If the iOS device has a screen size of 10.1" or greater, it requires E3/A3 or above licence. Any smaller devices are ok with the E1/A1 licence.

It would be worth checking out Mosyle's Partner program. Back when we last spoke to them in March, they weren't quite ready, but it seems to be live now. https://manager.mosyle.com/partners

I have run in to similar issues with direct booking to on-site Exchange. Best I could find, was that the Direct Booking feature was deprecated in Outlook 2013.

I would beware though, as voice prints would be classed as Biometric data, which requires MUCH greater scrutiny when it comes to personal information.

You would be able to yes. In the Office 365 control panel, you can tell the DNS wizard not to give you Exchange settings, so the Office 365 tenancy won't warn about missing autodiscover and MX, but will still allow the addresses as valid Aliases on your mailbox. It would be adviseable to configure the domain as 'Internal Relay' in the Exchange control panel also.

Further to @sted all of your OneDrive data is held in a SharePoint site, that's usually listed as *domain*-my.sharepoint.com in the SharePoint admin centre.

On my way in to work this morning, my local radio station kept going "Fourth of May be with you". They ended up with SO MANY comments from people about getting it wrong