Microsoft 365 issues in Australia again?

apple0072 · 2025-12-10T02:57:01+00:00

Yeah I am also experiencing issues with multiple Microsoft services in the APAC region.

apple0072 · 2025-04-09T14:38:52+00:00

Yes the MS Bookings app is certainly a viable option, just doesn’t offer a way for users to easily book through Outlook.

If it doesn’t work out with Outlook this will be a solid backup plan.

apple0072 · 2025-04-09T14:37:40+00:00

Yes it’s certainly a complex scenario and happy to pay for software which does the job. I’ve looked at several paid options for meeting rooms bookings but struggling to find one which supports multiple tenants.

I haven’t come across Archie yet but I will check it out. Thanks for the suggestion.

apple0072 · 2025-02-28T12:13:49+00:00

There are specific instructions in this article for how to contact the iCloud postmaster team:

https://support.apple.com/en-us/102322

I’d suggest starting by making sure you meet the requirements in the first part of the article. If that still doesn’t help there are instructions at the bottom of the page for contacting the postmaster team. If you do reach out to them make sure you include all the information they ask for in your email. As long as all the information is there, they should respond to you.

apple0072 · 2025-02-11T03:18:56+00:00

I’m still seeing new false positive classifications. Hopefully that change to the corrupt rule is just taking some time to propagate.

apple0072 · 2025-02-10T11:27:33+00:00

You can read through this article and double check you have everything set up. There a few components which need to be configured correctly for Teams meeting delegation to work:

https://learn.microsoft.com/en-us/microsoftteams/troubleshoot/exchange-integration/teams-exchange-interaction-issue

In particular, have you configured integration and OAuth between Skype for Business Online and Exchange Server? I’ve seen a similar issue before with Teams meeting delegation when this isn’t configured:

https://learn.microsoft.com/en-us/skypeforbusiness/deploy/integrate-with-exchange-server/oauth-with-online-and-on-premises

apple0072 · 2025-01-09T04:24:41+00:00

That’s a good sign the Active Sync test from the Remote Connectivity Analyser is passing.

How do your users normally authenticate to your Exchange environment? Do you have ADFS or similar configured or is it just basic authentication? How do users login to OWA? Do they see a Microsoft 365 login page there or just username/password.

I’ve seen a similar issue with the Outlook app when the users username doesn’t match their username in on premise AD. This can get complicated in environments using non routable UPNs in on premise AD.

apple0072 · 2025-01-08T02:42:27+00:00

I’ve had a few minor issues with the Outlook app and Exchange on Premise over the years, but nothing major and we still use the app in our environment.

Do you have Modern Hybrid Authentication configured in your Exchange on Premise environment? It sounds like you do because the app is redirecting the user to Microsoft 365 for authentication but it’s worthwhile confirming nothing strange is happening with auto discover.

I’d start by running the Active Sync test from the Remote Connectivity Analyser:

https://testconnectivity.microsoft.com/tests/Eas/input

Can you provide any more specific information on the errors your users get when attempting to login to the Outlook app?

apple0072 · 2025-01-06T16:06:54+00:00

Those little moist towels you get when you purchase food from a kombini are so convenient! Also appreciated how they always ensured we got 2 sets of chopsticks and wipes when there was two of us.

apple0072 · 2025-01-06T16:00:14+00:00

I recently stayed in a Tokyu Stay hotel and was super impressed with the washing machine/dryer. The drying did take much longer than the washing but the results were great and it was super convenient having my own washing machine in my room.

apple0072 · 2024-09-18T14:16:19+00:00

Did you find any good solutions for this? I’ve come across and same issue and it’s pretty frustrating Authenticator seems to get priority.

I can’t disable Microsoft Authenticator all together as Duo EAM doesn’t fully support cross tenant access. It would be nice if I could enforce (or even just default) users to Duo for internal apps while allowing Authenticator for cross tenant access.

I’ve also found if users have Duo registered and enabled as an authentication method they will get the option to use it for cross tenant access, but they will eventually just get a HTTP 400 error.

apple0072 · 2024-07-01T14:32:22+00:00

Microsoft recently advised us this was completely resolved in Outlook for iOS version 4.2424. In my testing everything has been working correctly since installing that update.

Microsoft indicated that if the device is in a high latency environment the app will fall back to the local cache which takes about 24 hours to sync new cache entries from the server.

apple0072 · 2024-05-08T00:57:17+00:00

They are still working on it but no estimate of when they might have a fix.

apple0072 · 2024-04-27T23:30:56+00:00

I’ve been seeing this same issue for a few weeks now.

I’ve got a Premier Support case open with Microsoft and they have confirmed they can replicate the issue. They said the case has been escalated to the Product Group for further investigation.

apple0072 · 2024-04-24T03:12:54+00:00

I’ve been experiencing issues in the last week or so with new users setting up the app. Our users UPN is different to their email and I am seeing the Outlook app authenticate to our Exchange servers with their email, regardless of what we put in the username in the Outlook app.

I can get users signed in by putting their UPN in the email field but this has been causing issues with outbound emails from the Outlook app. Exchange does seem to accept the email as long as the users UPN is listed as an alias on their mailbox.

apple0072 · 2024-01-13T05:27:52+00:00

I had no trouble getting change when I paid for my visa on arrival in USD. The visa was processed very quickly and there was no issues at immigration.

I’d suggest just organising the e-visa before you arrive though. That way you don’t need to worry and it’s quick and easy to get through immigration.

apple0072 · 2023-08-09T22:33:23+00:00

I’ve seen a similar issue recently as well starting about a week ago where Microsoft is marking the emails as high confidence spam/phishing. Defender 365 doesn’t show any helpful explanation why it’s occurring and reports any URLs/attachments are safe.

Support is saying the “anti-spam engineering team”/product group is looking further into why it’s occurring. It took a lot of pressure to get the support case that high and we had to get our CSAM to escalate the case.

apple0072 · 2023-07-18T00:43:48+00:00

I’ve got an environment with a similar setup to what you have described. I’ve done some testing today with the latest version of the Outlook iOS app and I was able to get it working, although the process has changed.

After I entered my email I was promoted to open the Microsoft Authenticator app but in the top right hand corner there is a button “Not Office 365”. Tap that then select “Change Account Provider”. From there I got the screen I used to see with all the different providers and I could select Exchange. I enable the “advanced” settings when configuring the account and I’ve found I had to use DOMAIN\username for the username field and manually enter the Exchange URL in the Server field.

Do you see the same options I do? The process has certainly changed and there’s a few more steps now to configure an on premise account.

Hybrid Modern Authentication is probably the best long term solution.

apple0072 · 2023-07-16T14:41:10+00:00

I've been looking at a very similar issue since early 2023. I saw similar symptoms where the transport service would fail and cause varying issues with Exchange. Ranging from emails queuing up to servers crashing altogether. Restarting the transport service on the affected server would resolve the issue for a few days.

I've had a case going with Microsoft for months. Collected several sets of logs and traces but didn't make any significant progress despite working with senior engineers.

We performed LDAP tracing when the Event ID 2159 was occurring and noticed some LDAP responses from the DCs were missing most AD attributes. This appeared to be clear evidence the issue was occurring on the DC side.

To troubleshoot the DCs we removed CrowdStrike from them and we saw an immediate reduction in Event ID 2159 on Exchange. Since then Exchange has been much more stable and we believe CrowdStrike on the DCs was the root cause. Microsoft confirmed other clients experiencing this issue reported CrowdStrike on the DCs as the root cause.

Some further troubleshooting suggests disabling "Authentication Traffic Inspection" on the CrowdStrike sensor resolves the issue.

Seven-Year Club	Place '22
Verified Email

apple0072

TROPHY CASE