Microsoft's press release — MSFT's reaction is being measured
MSFT's realized reaction is still being measured.
· PR Newswire · Press release · Realized reaction, point-in-time, zero look-ahead.
Microsoft announces quarterly earnings release date
Via PR Newswire
Reaction is being measured.
This event is recent. News Quantified labels the realized price reaction once the trading sessions after the news complete — point-in-time, with zero look-ahead. The measured move will appear here, and below in MSFT’s reaction history.
MSFT’s news landed in the after-hours window; the main session closed +0.00%.
- Mainprior session
- After-hours4:00 – 8:00 PM
- Overnightno tape
- Pre-market4:00 – 9:30 AM
- Main session9:30 AM – 4:00 PM
Segment widths are fixed, so two events on different days sit in comparable places. Hatched segments are real elapsed time with no tape to measure — the overnight halt is not a gap in the data. This event carries no intraday receipt time, so it is not pinned to a minute.
| Window | What it answers | Anchor price | Result |
|---|---|---|---|
| All | From the news to the first main-session close, across every session in between. | 529.58re-anchored to the first print after the news | +0.00% |
| After-hours | The move between the closing bell and the overnight halt. | — | not measured |
| Pre-market | The move between the pre-market open and the opening bell. | — | not measured |
| Main | The move inside the regular session, from the news to the close. | — | not measured |
The main-session result is measured upstream against the price at the news; the all-sessions result is computed here from its own anchor and close, so the two can differ in the last decimal. After-hours and pre-market are measured upstream but populate on a small minority of events, so this page does not request them. Those rows are unmeasured, not empty.
The same event measured across every session8
| Horizon | Reaction |
|---|---|
| 30 sec | +0.00% |
| 1 min | -0.04% |
| 5 min | -0.08% |
| 10 min | -0.75% |
| 30 min | +0.00% |
| 60 min | +0.00% |
| 90 min | +0.00% |
| 120 min | +0.00% |
Where this MSFT event came from, and what the tape did with it.
Microsoft issued a press release, carried via PR Newswire, on Oct 7, 2026. It was one of 3 Microsoft headlines News Quantified labeled that day, so its measurement window overlaps with the others on a shared tape. The same session also carried Microsoft's "CyberMaxx Builds Momentum with Recent Acquisition, Leadership…" and 1 other Microsoft headline, each measured on its own clock.
Against the price at the news timestamp, MSFT's reaction is still being measured. Because several releases shared that day, their measurement windows overlap and no single headline cleanly owns the move.
How this compares to MSFT’s usual reaction.
Across 2,000+ labeled events, MSFT’s median 30-minute reaction to all news is +0.02% (53% up); by the close it is -0.11%.
| Middle 50% of MSFT reactions | -0.33% to +0.40% |
|---|---|
| Median reaction (30-min) | +0.02% |
| Measured reactions | 2,000+ |
Half of all Microsoft news events land between -0.33% and +0.40% at 30 minutes; this one is a single draw from that distribution.
You just saw one reaction. There are 26M+ more.
See the full MSFT reaction history →What the MSFT tape carried around this event.
The 20-day average true range into this session was 11.16. MSFT carries no market-cap or price-to-earnings figure on this record, and no short interest, so none is shown.
Email me when MSFT moves on news.
One email per qualifying move — the headline, the measured reaction, and how it compares to MSFT's baseline. Nothing else.
How comparable MSFT events have landed.
Across 5 other recent Microsoft press release events, the median close-day reaction was -0.22%. Each is measured the same way, from its own news timestamp.
8 more MSFT events, each measured the same way.
Recent MSFT events, each with its measured reaction8
That same day, across the market6
Same measurement, same clock, different names — each headline measured from its own news timestamp, point-in-time.
Peer tickers, measured the same way4
Every US ticker is measured the same way, from its own news timestamp. Browse all tickers →
MSFT carried 2 other records that day.
Each was measured the same way, from its own timestamp.
| Record | Event | 5-min | To close |
|---|---|---|---|
| CyberMaxx Builds Momentum with Recent Acquisition, Leadership Investments, Email Security Offerings, and AI-Powered MaxxMDR Innovation | Press release | -0.41% | -0.22% |
| King Celebrates Candy Crush Saga® With Guinness World Records™ Title | Press release | -0.41% | -0.22% |
How the numbers are made.
How was MSFT's 5-minute reaction measured?
From the news timestamp, not the trading day: News Quantified takes the last trade before this press release as the base price and measures the move five minutes of trading later — point-in-time, zero look-ahead. The same clock produced the to-close figure.
What is Microsoft's median reaction, and how does this event compare?
Microsoft's median is drawn from 2,000+ labeled events; at 30 minutes it sits at +0.02%, and -0.11% by the close. This event's move is one draw from that distribution — ordinary or outlier, the chart's median ticks show which.
3 Microsoft headlines shared Oct 7, 2026. Whose reaction is this?
Each of the 3 same-day Microsoft events is measured from its own timestamp, but their windows overlap on one tape, so we show the cluster rather than pretending a single headline owns the move.
Does a measured reaction predict Microsoft's next reaction?
No. a measured reaction is a realized fact about Oct 7, 2026, not a forecast. Past reactions describe a distribution; they say nothing certain about any future move.
How to cite this reaction.
News Quantified. "Microsoft announces quarterly earnings release date." MSFT realized price reaction, Oct 7, 2026. Retrieved from https://newsquantified.com/tickers/msft/news/microsoft-announces-quarterly-earnings-release-date-2026-10-07
Canonical URL: https://newsquantified.com/tickers/msft/news/microsoft-announces-quarterly-earnings-release-date-2026-10-07
Query this dataset via the API & MCP →