HPlum78

https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/landing-zone/ The above is useful for planning your cloudy environment(s).

I have posted regarding this in the past look em up, but the TLDR is essentially down to flavour of cloud. By that I mean if you are going to do a lift and shift servers to cloud migration IaaS then you are not going to save a penny (if cost is your only driver) if you run web servers then migration of these to PaaS you should realise a saving. Then there is SaaS where you should be able to garner a better saving again. But that is if you are solely basing you cloud journey on cost benefits alone, there is lots more to consider when thinking of cloud migration.

Sorry @chaplic was not being funny with u there I agree best way to go for sure (and version 4 :-D)

Did any one say phone microsoft?

Need to see the trace logs from the Bromcom side to see what it thinks has happened.

So it seems from your post that the mails never left Bromcom as they never appear in the message trace? (Are we suggesting that the mail has been sent but MS is dropping those mails?(that is a whole other issue and you would need bullet proof evidence of that...))

4 When outbound message volumes surpass the message rate limit, any excess in message submission will be throttled and successively carried over to the following minutes. This will typically not block the sender's account, but Exchange Online isn't suited to accommodate bulk-mailing scenarios. For this use case, options 2 and 3 here are recommended instead. That is note 4 on the rules of engagement for mail submission. I don't know Bromcom at all, what are the options for mail delivery? If its cloudy then there is little point standing up an on premise SMTP solution, but there must be a way to submit mail in to O365 in some other manner?

From a quick look as long as you have not tried to make it primary in any way in your original tenancy you should not have an issue standing SP/ OneDrive in a new tenant. But the deletion wait time is still a thing mind.

Oh and that's after removing it from your ogrinal tenant you will have to wait.

So if you have added it to an existing tenancy you will have to wait for 3 maybe 5 days before you can add it to another tenancy from memory. Also I don't know that you will be able to use SP and OneDrive but that may have been fixed now.... Will have a look see.

So just running that code as is now I am in front of a box gives me the following error: Unexpected attribute 'cmdletbinding'.... Now this can be made to continue with caveats, and depends on if this is a terminating or none terminating error, and what $ErrorActionPreferance is set to. The upshot is that running that interactively and I guess that you have $ErrorActionPreferance set to silentlycontinue? Then the script will run. However when you run it as a schedule task it fails as that erroraction will be set to stop. In any case ditch the [cmdletbinding()] and put in some logging (see my previous posts on this topic) and don't forget you can debug PS scripts and mimic them being run none interactively. TBH I would functionlise this moving forward but initially do it dirty and get it working.

Ah yeah missed the rarely used bit in that case blow it away :-D

Is that all the code? Now I am on my phone so could be missing something here but it looks like it starts with [cmdletbinding()] If that is true then in my mind that will fail as that declaration forms part of function verb-noun.... and will error, running scripts interactively and none interactively will alter things in sutal ways. That said running that chunck of code should produce an error either way round. If you could run just that code and paste the ps output or dig out the whole of that function that would be useful.

I am not sure that I would stand up a new tenant and migrate unless I really had to... if your using SP online then MS have functionality for this that makes changing the primary Domain name simple (also takes care of OneDrive). There is a ton of things to consider when migrating between tenants. In saying that is not impossible and as it is late I will not unpick the pros and cons of this, also you do not say if its SP online, if you are using EXO if your current Domain is Federated or not... the list goes on and all these factors and more need to be considered.

What is the 'short distance'? And saying adjacent are you able to reach it without crossing on to someone else's land?

If you are an MS cloudy school would you not consider MS Bookings? You can write the Integration you want...

https://practical365.com/report-room-mailbox-statistics/ This will help you along and stop me reinventing the wheel...

Some insights here: https://practical365.com/microsoft-365-outage-january-2023/

Yep you made a mistake if I get rid of you then that's our loss if I keep you this will not happen again. Also let's be fair here there is no one person involved in a reconfiguration of how the underlying routing works in the MS cloudy environment. This has passed a few people's eyes and probably some AI before they took down their entire operation!

@Andrew_C if no one can get to it, is that not safer? MS has just got us all cyber essentials certified...

And I do believe that hosted sims is in Azure.

Yeah the issue with having the status page behind a login is that when everything is not working you cannot see the notifications!

We use WSUS here and have ~700 servers that are patched via this. We leverage groups to split the servers in to maintance windows so they all don't go at the same time along with some scripts that randomise the install within that maintance window for install and restarts (this is to ensure the underlying storage ain't flattened by all the servers installing and then restarting in a massive batch!). We then have another script that checks for pending reboots as sometimes when patches/ updates are installed after the reboot they have not quite done!

Yeah absolutely and it comes down to how the individual organisations what's to approach this. Let's be certain we should be protecting identities with a separate factor. It's then a policy decision on how that is implemented (if you are going to supply tokens and all that) and like I have said in the past policy should not be the IT departments arena.

But now we have pulled google into the fold context-aware access is googles implementation of conditional access, I am not as clued up on these as MS's offering but from my previous experience you are able to set policies based on ip address and second factor auth requirements and such likes. But without dusting off my Google knowledge I will defer any further comments to someone who is knee deep in that cloudy based environment...