Why were Microsoft FBL reports not being received in September 2020?

Summary

In September 2020, multiple email service providers (ESPs) reported issues with receiving Feedback Loop (FBL) reports from Microsoft. The disruption began around mid-September. Potential causes include Microsoft infrastructure changes impacting SPF/DKIM validation and delivery speeds, occasional Microsoft FBL outages, glitches in Microsoft's internal systems, and changes in how Microsoft processes FBL data. Some suggest checking Microsoft's status page, contacting support, and waiting a few days for resolution. Authentication issues, particularly with SPF, DKIM, and DMARC implementation, along with temporary DNS issues affecting authentication may have caused FBL problems. Others suggested double-checking FBL setup, monitoring IP reputation via Microsoft's SNDS program, and closely monitoring delivery metrics to identify potential issues. Data privacy considerations impacting how Microsoft processed and shared data, or reputation-based suppression of FBL reports due to increased complaints or decreased engagement were also possible causes.

Key findings

  • Widespread FBL Disruption: Multiple ESPs experienced a cessation of Microsoft FBL reports around mid-September 2020.
  • Infrastructure and System Issues: Microsoft infrastructure changes, system glitches, outages, or changes in FBL data processing may have contributed to the problem.
  • Authentication Problems: Issues with SPF, DKIM, or DMARC implementation, and temporary DNS problems could impact FBL reporting.
  • Reputation Impacts: Sudden changes in sender reputation may cause Microsoft to suppress FBL reports.
  • Data Privacy Changes: Changes in data privacy standards, causing changes in the way FBL data is sent.

Key considerations

  • Check Status and Contact Support: Verify Microsoft's status page for known issues and contact support if necessary.
  • Review FBL Setup: Double-check FBL setup to ensure proper configuration.
  • Monitor Reputation and Metrics: Monitor IP reputation using Microsoft's SNDS and track delivery metrics for abnormalities.
  • Authentication Implementation: Ensure SPF, DKIM, and DMARC are properly implemented.
  • Adapt to Privacy Standards: Stay informed about and adapt to evolving data privacy standards.
  • Watch DNS Propagation: Ensure SPF and DKIM record changes propagate correctly.

What email marketers say
16Marketer opinions

In September 2020, several email service providers (ESPs) experienced issues with receiving Feedback Loop (FBL) reports from Microsoft. The disruptions generally started around mid-September. Possible causes include Microsoft infrastructure changes impacting SPF/DKIM validation and delivery delays, occasional outages on Microsoft's end, and potential glitches in Microsoft's internal systems. Some suggest checking Microsoft's status page for known outages or contacting Microsoft support. Other suggestions included temporary glitches, or Microsoft changing the way they process FBL data. It was recommended to double-check FBL setup, monitor IP reputation using Microsoft's SNDS program to identify filtering issues, and to monitor delivery metrics.

Key opinions

  • Widespread Issue: Multiple ESPs reported a cessation of Microsoft FBL reports around the same time in September 2020.
  • Infrastructure Changes: Microsoft infrastructure changes may have impacted SPF/DKIM validation and delivery speeds.
  • Potential Glitches: Temporary glitches or internal system issues on Microsoft's end could be responsible.
  • Possible Changes to FBL processing: It's possible that Microsoft changed the way FBL data is processed.

Key considerations

  • Check Microsoft Status: Consult Microsoft's status page or contact support to identify known outages.
  • Verify FBL Setup: Double-check FBL setup and ensure it's correctly configured.
  • Monitor IP Reputation: Use Microsoft's SNDS program to monitor IP reputation and complaint rates.
  • Monitor Delivery Metrics: Proactively monitor deliverability metrics to identify and resolve potential issues.
  • Check DNS Settings: Ensure SPF and DKIM records are correctly configured and propagating properly to avoid authentication failures that affect FBL reporting.
Marketer view

Marketer from Email Geeks shares their FBL reports seemed to stop on the 17th but then came back and were backdated.

September 2021 - Email Geeks
Marketer view

Marketer from Email Geeks shares that several ESPs are facing the issue of not receiving FBL complaints from Microsoft since Thursday evening (UTC time). They have started a thread on Mailop and suggest verifying if others are also impacted.

July 2021 - Email Geeks
Marketer view

Email marketer from EmailGeeksCommunity.com recommends double-checking your FBL setup, even if it was working before, especially after a reported outage.

July 2024 - EmailGeeksCommunity.com
Marketer view

Email marketer from Mailop.org shares experiencing missing FBL reports. After contacting Microsoft support, the reports started flowing again after a few days. This suggests a possible issue with their internal systems or a temporary outage.

May 2023 - Mailop.org
Marketer view

Email marketer from Reddit mentions that Microsoft sometimes has outages with their FBL, and to check the status page.

February 2024 - Reddit
Marketer view

Email marketer from Email Deliverability Blog responds that FBL systems are complex, and temporary issues can arise due to software bugs, server maintenance, or network problems on Microsoft's end.

August 2023 - Email Deliverability Blog
Marketer view

Marketer from Email Geeks confirms that FBL reports stopped around the beginning of the 18th as well.

February 2023 - Email Geeks
Marketer view

Email marketer from Tech Email Forum shares the DNS issues on the sender side causing problems, sometimes SPF or DKIM records might not propagate quickly enough after changes, leading to authentication failures that affect FBL reporting.

October 2023 - Tech Email Forum
Marketer view

Marketer from Email Geeks confirms they are now receiving FBL feeds.

February 2022 - Email Geeks
Marketer view

Email marketer from EmailDeliveryBlog.net explains using Microsoft's SNDS program to monitor your IP reputation, and if the tool shows an increase in complaints around the time the FBL stopped, it is possible there was a filtering issue at Microsoft which prevented the delivery of FBL reports.

December 2021 - EmailDeliveryBlog.net
Marketer view

Email marketer from Email Marketing Forum says it could be a temporary glitch on Microsoft's end, rather than a configuration issue on the sender's side. He recommends waiting a few days and monitoring.

May 2023 - Email Marketing Forum
Marketer view

Marketer from Email Geeks confirms not receiving FBL reports since September 13th.

July 2021 - Email Geeks
Marketer view

Email marketer from EmailMarketingTips.org thinks Microsoft might have changed the way they process FBL data, resulting in a temporary cessation of reports while the system adjusted.

June 2024 - EmailMarketingTips.org
Marketer view

Marketer from Email Geeks confirms that the last FBL report was received on midnight of the 18th.

August 2021 - Email Geeks
Marketer view

Marketer from Email Geeks confirms experiencing the same issue.

July 2021 - Email Geeks
Marketer view

Email marketer from Mailop.org suggests the cause may be related to Microsoft infrastructure changes. Microsoft often makes changes to their infrastructure, and it is likely related to the FBL delays. The changes may also have impacted the speed of SPF/DKIM validation, resulting in delivery delays.

June 2023 - Mailop.org

What the experts say
3Expert opinions

Experts suggest that the disruption in Microsoft FBL reports in September 2020 could stem from several factors. Data privacy considerations might have led to changes in Microsoft's data processing and sharing practices, causing temporary disruptions. Common issues such as misconfiguration, blocklisting, and network glitches could also impact FBL report reception. Additionally, a sudden change in sender reputation, such as a spike in complaints, might trigger Microsoft to suppress FBL reports as a spam mitigation measure.

Key opinions

  • Data Privacy Impact: Data privacy considerations could cause changes in how Microsoft processes and shares FBL data.
  • Common FBL Issues: Misconfiguration, blocklisting, and network glitches are potential causes of FBL report disruption.
  • Reputation-Based Suppression: Sudden changes in sender reputation can trigger Microsoft to suppress FBL reports.

Key considerations

  • Adapt to Privacy Standards: Stay informed and adapt to evolving data privacy standards to minimize disruptions.
  • Proactive Monitoring: Proactively monitor deliverability metrics to identify and resolve potential issues with FBL reception.
  • Maintain Sender Reputation: Ensure a consistent sender reputation to avoid being flagged for spam mitigation measures.
Expert view

Expert from Word to the Wise explains that data privacy considerations can lead to changes in how Microsoft processes and shares FBL data, potentially causing temporary disruptions or delays in receiving reports. She highlights the importance of adapting to evolving privacy standards.

March 2024 - Word to the Wise
Expert view

Expert from Spam Resource emphasizes that sudden changes in sender reputation can trigger Microsoft to temporarily suppress FBL reports as part of their spam mitigation efforts. A sudden spike in complaints or a sudden drop in engagement can trigger this.

May 2022 - Spam Resource
Expert view

Expert from Word to the Wise describes common issues impacting Microsoft FBL report reception like misconfiguration, blocklisting, or network glitches. He suggests proactively monitoring deliverability metrics to identify and resolve potential issues.

September 2021 - Word to the Wise

What the documentation says
4Technical articles

Microsoft's documentation highlights several factors impacting FBL reception. Participating in Outlook.com's FBL requires implementing SPF, DKIM, and DMARC authentication. Monitoring the SNDS portal provides insights into mail traffic and complaint rates, indicating potential FBL issues. Ensuring proper configuration of systems to receive and process feedback data is crucial, alongside reviewing FBL documentation for troubleshooting. The RFC documentation explains the ARF format, emphasizing clear identification and processing of feedback loops, suggesting any changes by Microsoft to its FBL processing might affect ARF parsing.

Key findings

  • Authentication Required: Participation in Outlook.com FBL necessitates the implementation of SPF, DKIM, and DMARC.
  • SNDS Monitoring: Microsoft SNDS provides data on mail traffic and complaint rates to diagnose FBL problems.
  • System Configuration: Properly configured systems are essential for receiving and processing FBL data.
  • ARF Format: Changes to Microsoft's FBL processing might affect the parsing of ARF reports.

Key considerations

  • Implement Authentication: Ensure proper implementation of SPF, DKIM, and DMARC for FBL participation.
  • Utilize SNDS: Regularly monitor the SNDS portal for insights into mail traffic and potential issues.
  • Review Configuration: Verify that systems are correctly configured to receive and process FBL data.
  • Troubleshooting: Consult FBL documentation for troubleshooting tips and best practices.
Technical article

Documentation from Microsoft SNDS recommends monitoring the SNDS portal to get the most up-to-date information about your mail traffic including complaint rates, which may indicate FBL issues.

November 2023 - Microsoft SNDS
Technical article

Documentation from RFC Editor (RFC 5965) explains the ARF format for FBL reports, emphasizing the need for clear identification and processing of feedback loops. If Microsoft made changes to its FBL processing, it might have temporarily affected the ARF parsing.

November 2023 - RFC Editor
Technical article

Documentation from Microsoft Postmaster suggests that if you aren't receiving FBL data, ensure that your systems are properly configured to receive and process the feedback data. They also recommend reviewing their FBL documentation for troubleshooting tips.

March 2022 - Microsoft Postmaster
Technical article

Documentation from Microsoft Documentation states that to participate in the Outlook.com FBL, you need to implement certain authentication standards such as SPF, DKIM, and DMARC.

June 2024 - Microsoft Documentation