.NET software engineer & Azure Architekt. I automate email in M365 and build tools and add-ins for Outlook and MS Teams. I'm also the creator auf AutoReply365.
I built @AutoReply365: automated replies for shared mailboxes in Exchange Online.
Looking for feedback from M365 admins. Mention or DM me for free usage in your own tenant.
After bringing subagents to Codex on Windows just recently. "Fast mode" is now also supported.
I switched to Codex last week and since it has been a game changer.
#codex#openai#windows
Microsoft Foundry (new) is randomly throwing "Error: too_many_requests: Too Many Requests". Location: GermanyWestCentral, Model: GPT 4.1.
It's a test setup. I'm 100% sure, that I have not sent too many requests. Anyone else seeing this? #microsoft#foundry
Let’s Encrypt is adding DNS-PERSIST-01: publish one persistent DNS TXT record per ACME account instead of updating it every renewal –> faster, safer, and easier automation. Wildcards supported. Targeting Q2 2026
#letsencrypt#ssl
When was the last time you checked your Enterprise Applications in Microsoft Entra?
Take the 2 minutes. You might be surprised what’s in there. 👀
#MicrosoftEntra#Identity#CloudSecurity
Seeing huge (> 40 KB!) X-Microsoft-Antispam-Message-Info headers on messages coming from Exchange Online since about 04:30 am CET. Any know issues? @MSFT365Status
@MSFT365Status The issues are on our customer's side which use our signature add-on service. They've already raised a ticket. How can we continue with this?
@MSFT365Status Seeing high volume of false-positiv messages in quarantine after emails went through an email signature add-on service. Any know issues?
Is this related to https://t.co/xv7c0BvPkB?
Mail flow is compliant with https://t.co/GtKUxIlUI4
We've disabled a rule change causing legitimate emails to be marked as spam, and we're starting to see recovery. Additional details can be found in the admin center under EX682041.
@MSFT365Status Today we've seen legitimate EXO traffic (especially out of office messages) coming to our servers from IP range 40.95.0.0/16, which is the "high-risk delivery pool", and therefore not on the M365 endpoints list (https://t.co/3crLDxW2ix). Is there an issue?
The best are the best no matter where:
"The people who didn't do any work at home never did any work in the office. ... Hard workers are hard workers no matter where they operate."
A tiny thought in @farnamstreet's newsletter: https://t.co/nhGV6L3i18
Users are reporting receiving an error including "550 5.4.1 Recipient address rejected: Access denied" and we are investigating further. More details can be found in the admin center under EX522020.
We're investigating an issue wherein users may be unable to access their Exchange Online mailboxes via any connection method. Additional details can be found within the Service Health Dashboard under EX522020.
@MSFT365Status Seeing an increasing amount of "550 5.4.1 Recipient address rejected" errors on EXO inbound connectors for different tenants. Any know issues?
We're investigating an issue wherein users may be unable to access their Exchange Online mailboxes via any connection method. Additional details can be found within the Service Health Dashboard under EX522020.