Business Leaders Must Pair Recovery With a Documented Assessment of Ongoing Operational-Disruption Exposure — Data Protection Duties Include Keeping Systems Available and Operations Running
Business leaders of organizations impacted by system outages like yesterday’s Microsoft systems outage need to understand that their legal responsibility for responding to the incident doesn’t end with restoring their organization’s email, Teams, SharePoint and other Microsoft 365 functions after yesterday’s outage. While restoring normal systems operations is the immediate job, leaders should ensure their organizations pair their operational recovery with a documented assessment of ongoing operational disruption risk exposure to future systemic risks and implementation of appropriate risk mitigation actions to fulfill organizational duties to keep systems available and operations running included in legal data protection responsibilities.
Cybersecurity, health privacy, financial privacy, securities, employee benefit, and other federal, state and international data protection laws treat the availability of systems and data — and the organization’s ability to keep operating and to restore access in a timely way when a critical service fails — as a core component of the duty to safeguard data and systems. Microsoft’s statement that the event was not a cyberattack does not take it outside those obligations.
Every organization that depended on the affected services and others with similar dependencies on other operating systems on should now work with qualified legal counsel within the scope of attorney-client privilege to conduct, document, and act on a risk assessment of its ongoing exposure to disruption of mission-critical third-party platforms, and should be able to show regulators, auditors, plaintiffs, insurers, and its own board that it did so.
What Happened
Beginning shortly before 1:00 p.m. Eastern on Thursday, November 12, 2026, Microsoft customers in the Americas began losing access to Exchange Online mailboxes across multiple connection methods. The disruption spread to Outlook (web, desktop, and mobile), Teams, SharePoint Online, OneDrive, Copilot, Planner, Power BI, Microsoft Defender XDR, and other Microsoft 365 services that interact with Exchange Online, and to third-party applications that connect to them. It continued through the Asian business day and into Friday, November 13, with Microsoft reporting partial recovery, servers that became unresponsive again once traffic returned, and no firm timeline for full restoration as of 5:00 a.m. on November 13, 2026
Lie previous disruptions of the Microsoft 365 operating system that caused widespread disruptions earlier this year, Microsoft has publicly stated that it has no indication the event resulted from malicious or cyber activity. Its preliminary explanation is that a server process responsible for establishing secure connections became overloaded, servers stopped processing requests, and the resulting shift of traffic overloaded remaining infrastructure. Microsoft has said it will issue a Post-Incident Report with root cause and repair items. Administrators can track the event in the Microsoft 365 admin center under incident IDs EX1550543 and MO1550821.
The consequences were not limited to inconvenience. Microsoft’s outage reports on November 12 reached 74 countries and territories in about an hour on Downdetector. Media reports describe impacts on federal agency and congressional email, with the U.S. House of Representatives confirming its users were affected. NBC News, Microsoft services hit by major outage across the world (Nov. 12–13, 2026); Reuters, Microsoft outage drags on for hours, disrupting Outlook, Teams for businesses and governments (Nov. 13, 2026) (via The Korea Times). Municipal services were disrupted, including in the Texas cities of Sugar Land, Pearland, and League City, and local governments told residents to call rather than email. KPRC Click2Houston, Microsoft 365 outage disrupts Outlook email access, company says (Nov. 12, 2026); CNN, Massive Microsoft outage disrupts businesses, schools and governments around the world (Nov. 12, 2026). Court and justice-system operations were affected, from a U.S. jurisdiction requiring bond to be posted in person at the jail to lost live feeds from Australian courts, and schools resorted to texting parents. NBC News; CNN. Abroad, New Zealand government agencies reverted to manual processes, with Immigration New Zealand pausing visa processing. AAP, Microsoft outage recovery ‘not progressing as expected’ (Nov. 13, 2026) (via New England Times). And at least one public company, Workhorse Group, postponed its third-quarter earnings release from November 12 to November 16, citing business disruptions caused by the outage. Reuters (via The Korea Times); CNN, Microsoft outage live updates (Nov. 12, 2026).
Why “Not a Cyberattack” Does Not End the Legal Analysis
Most data protection regimes are built on the familiar confidentiality–integrity–availability framework. An outage that leaves an organization unable to reach its own records, communicate with customers, patients, plan participants, or regulators, process transactions, or meet legal deadlines is an availability-failure, whatever caused it. Several regimes say so expressly:
- The HIPAA Security Rule requires covered entities and business associates to ensure the confidentiality, integrity, and availability of all electronic protected health information they create, receive, maintain, or transmit, and defines availability as data being accessible and usable on demand by an authorized person. 45 C.F.R. § 164.306(a)(1); 45 C.F.R. § 164.304.
- The EU General Data Protection Regulation requires controllers and processors to implement measures ensuring the ongoing availability and resilience of processing systems and the ability to restore availability of and access to personal data in a timely manner after a physical or technical incident. Regulation (EU) 2016/679, art. 32(1)(b)–(c).
- The SEC’s cybersecurity disclosure rules define a “cybersecurity incident” by reference to occurrences that jeopardize the confidentiality, integrity, or availability of a registrant’s information systems, and require disclosure of processes to oversee and identify risks associated with third-party service providers. 17 C.F.R. § 229.106(a), (b); SEC Release No. 33-11216 (July 26, 2023). Whether a non-malicious vendor outage is an “unauthorized occurrence” triggering Form 8-K Item 1.05 is a fact-specific question, but the risk-management and governance disclosures plainly reach third-party platform dependency.
- The NIST Cybersecurity Framework 2.0 — the reference framework many statutes, regulators, contracts, and safe-harbor laws point to — places cybersecurity supply chain risk management in its Govern function and makes Recover a co-equal function. NIST CSWP 29, The NIST Cybersecurity Framework (CSF) 2.0 (Feb. 26, 2024); see also NIST SP 800-34 Rev. 1, Contingency Planning Guide for Federal Information Systems.
In short, the legal question after yesterday is not only whether data was compromised. It is whether the organization had reasonably assessed and mitigated the risk that a single critical provider’s failure could stop its operations, and whether it can prove it.
Where the Legal Obligations Come From
Legal responsibility to take appropriate steps to safeguard computer operating systems and data operational integrity and accessibility can arise from a myriad of sources including the following:
Securities Law and Public-Company Governance
- Risk management and governance disclosures. Form 10-K Item 1C requires public companies to describe their processes for assessing, identifying, and managing material cybersecurity risks, including risks from third-party service providers, and board and management oversight of those risks. 17 C.F.R. § 229.106(b)–(c). Disclosures made before yesterday should be checked against what the outage actually revealed about the company’s dependency and recovery capability.
- Risk factors. Material risks from concentration on a single cloud productivity and communications platform belong in a fair risk-factor presentation; hypothetical framing of a risk that has now materialized can draw scrutiny. 17 C.F.R. § 229.105.
- Current reporting and disclosure controls. Companies whose operations, financial reporting close, or investor communications were affected should evaluate Form 8-K obligations, earnings-release timing, and whether disclosure controls and procedures functioned when primary communication channels were down.
- Regulated financial firms. Broker-dealers must maintain and annually review written business continuity plans addressing, among other things, data backup and recovery and alternate communications with customers and regulators. FINRA Rule 4370. Amended Regulation S-P requires covered institutions to maintain incident response programs and oversee service providers. 17 C.F.R. part 248, subpart A SCI entities have separate systems-resiliency and business continuity duties under Regulation SCI, 17 C.F.R. § 242.1001.
- Director oversight. Under Delaware’s Caremark doctrine, directors face potential liability for failing to make a good-faith effort to implement and monitor reporting systems for mission-critical compliance risks. In re Caremark Int’l Inc. Derivative Litig., 698 A.2d 959 (Del. Ch. 1996); Stone v. Ritter, 911 A.2d 362 (Del. 2006) (adopting the Caremark oversight standard); Marchand v. Barnhill, 212 A.3d 805 (Del. 2019). For most enterprises, the continuity of core communications and records systems is mission-critical. Board minutes should reflect that directors received and acted on a post-incident report.
HIPAA — Covered Entities, Business Associates, and Group Health Plans
Health care providers, employers sponsoring group health plans, health insurance, health data and information technology, and their service providers regulated by the Health Insurance Portability and Accountability Act (“HIPAA”) Privacy and Security requirements face specific mandates under HIPAA including:
- Risk analysis and risk management. Covered entities and business associates must conduct an accurate and thorough assessment of risks to the confidentiality, integrity, and availability of ePHI and implement measures to reduce those risks to a reasonable and appropriate level. 45 C.F.R. § 164.308(a)(1)(ii)(A)–(B). A material availability event involving a platform that stores or transmits ePHI is a trigger to update the analysis.
- Contingency plan. The Security Rule already requires a data backup plan, disaster recovery plan, and emergency mode operation plan, and addresses testing and revision procedures and applications and data criticality analysis. 45 C.F.R. § 164.308(a)(7). Yesterday was, in effect, an unscheduled test. Results should be documented.
- Business associate oversight and documentation. Cloud and productivity providers that maintain ePHI are business associates; contracts must satisfy 45 C.F.R. § 164.314, and policies, procedures, and required assessments must be documented and retained for six years. 45 C.F.R. § 164.316.
- Pending rule. HHS’s January 6, 2025 proposed overhaul of the Security Rule would, among other things, require written procedures to restore critical systems and data within 72 hours, criticality-based restoration ordering, and business associate notice within 24 hours of contingency-plan activation. 90 Fed. Reg. 898 (Jan. 6, 2025). The proposal is not final. In the most recent Unified Agenda of Regulatory and Deregulatory Actions, HHS moved the rulemaking (RIN 0945-AA22) from the Final Rule Stage to Long-Term Actions and now projects final action for July 2027, replacing the May 2026 target in the Spring 2025 agenda. Office of Information and Regulatory Affairs, Unified Agenda, RIN 0945-AA22, HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information (Long-Term Actions; final action 07/2027); see Unified Agenda publication history for RIN 0945-AA22. Unified Agenda dates are planning estimates, not commitments, and the Federal Register still lists only the proposed rule under this RIN. Until a final rule is published, the current Security Rule remains fully enforceable. Organizations that measure yesterday’s recovery against the proposed 72-hour benchmark will be better positioned whatever the final rule says.
- Plan sponsors. Group health plan sponsors should confirm that plan documents, business associate agreements with TPAs and vendors, and plan-sponsor safeguards address availability and continuity, not only breach notification.
FTC Safeguards Rule, Section 5, and State Financial Regulators
Organizations also may bear responsibility under Federal Trade Commission (“FTC”) and other rules such as the following:
- Non-bank financial institutions subject to the FTC Safeguards Rule — including many auto dealers, tax preparers, mortgage brokers, and payment and lending businesses — must base their information security program on a written risk assessment, oversee service providers, periodically reassess risks, and maintain a written incident response plan. 16 C.F.R. §§ 314.4(b), (f), (h).
- New York DFS-regulated entities must maintain written business continuity and disaster recovery plans designed to ensure availability and functionality of information systems and continued operation of the business, train personnel, and test plans at least annually, alongside third-party service provider policies. 23 NYCRR §§ 500.11, 500.16 (text available through the NYDFS Cybersecurity Resource Center).
ERISA Plan Fiduciaries and Benefit Plan Administration
Along with any health plan specific HIPAA responsibilities, employee benefit plan fiduciaries and their sponsors also should consider potential responsibilities under the Employee Retirement Income Security Act. (“ERISA”).
The Department of Labor has made clear that ERISA fiduciaries have a responsibility to mitigate cybersecurity risks, and its Cybersecurity Program Best Practices — which DOL has confirmed apply to all ERISA-covered plans, including health and welfare plans — call for formal, documented risk assessments, business resiliency programs addressing business continuity and disaster recovery, and appropriate service provider oversight. U.S. Dep’t of Labor, EBSA, Cybersecurity Guidance. Fiduciaries should document how they evaluated the dependence of plan administration and recordkeepers on the affected services.
Also, plans that rely on email under the DOL electronic disclosure rules should confirm that required disclosures sent during the outage were actually delivered and that invalid or bounced addresses were handled as the rules require. 29 C.F.R. § 2520.104b-1(c); 29 C.F.R. § 2520.104b-31. Benefit claim and appeal decisions and COBRA notices with regulatory deadlines should be audited for any items due on or around November 12–13. 29 C.F.R. § 2560.503-1; 29 C.F.R. § 2590.606-4.
Employment and Wage-Hour Consequences
Businesses also should ensure that the outage does not cause their organization to violate wage and hour and other relevant employment related responsibilities.
- Non-exempt employees who reported to work but could not perform their duties because systems were down are generally “engaged to wait,” and that time is compensable under the Fair Labor Standards Act (“FLSA”). 29 C.F.R. § 785.15. Steps also should be taken to ensure capture and retention of FLSA required records of nonexempt employee time.
- Employers generally may not reduce an exempt employee’s salary for absences occasioned by the employer or its operating requirements when the employee is ready, willing, and able to work. 29 C.F.R. § 541.602(a).
- Where timekeeping, scheduling, or payroll systems depended on affected services, employers should reconstruct and preserve accurate hours-worked records. 29 C.F.R. § 516.2. Continuity plans should include a non-Microsoft fallback for time capture and for urgent workforce communications, including safety notices.
Texas Law
The outage also may create responsibilities and risks under Texas or other applicable state laws. For instance, in Texas:
- Businesses must implement and maintain reasonable procedures, including appropriate corrective action, to protect sensitive personal information from unlawful use or disclosure. Tex. Bus. & Com. Code § 521.052(a).
- Effective September 1, 2025, Texas businesses with fewer than 250 employees that own or license computerized data containing sensitive personal information can shield themselves from exemplary damages in actions arising from a breach of system security if they implemented and maintained a cybersecurity program conforming to an industry-recognized framework at the time of the breach. Tex. Bus. & Com. Code ch. 542. The safe harbor is keyed to breaches, not outages, but a documented, framework-based program — including continuity and recovery controls — is exactly the evidence both the safe harbor and a reasonableness defense require.
- Controllers subject to the Texas Data Privacy and Security Act must establish, implement, and maintain reasonable administrative, technical, and physical data security practices. Tex. Bus. & Com. Code ch. 541.
Cross-Border Operations
▪ Beyond GDPR Article 32, EU financial entities subject to the Digital Operational Resilience Act must manage ICT third-party risk, maintain ICT business continuity and response and recovery plans, and assess concentration risk from critical ICT providers. Regulation (EU) 2022/2554 (DORA). Essential and important entities under NIS2 must address business continuity, backup management, disaster recovery, and supply chain security. Directive (EU) 2022/2555, art. 21. Multinational employers should coordinate assessments across jurisdictions rather than run them in silos.
Contracts and Insurance
Outages also implicate contractual and insurance risks and responsibilities. Among other things, organizations should:
- Review customer contracts for uptime, service-level, and notice commitments the outage may have triggered, and for force majeure language that may or may not excuse a failure caused by a vendor’s outage.
- Microsoft’s service-level remedies are typically limited to service credits with short claim windows; calendar the claim deadline now.
- Review cyber, business interruption, and contingent business interruption coverage for “system failure” and dependent-business provisions, waiting periods, and notice requirements. Give notice promptly where losses may exceed retentions.
Recommended Actions by Stakeholder
These and other legal implications provide a strong imperative for organizations and their leaders to take actions even after full restoration of their Microsoft operating systems to normalcy.
The first step in this risk mitigation process generally should be to engage qualified outside legal counsel to guide and to enable the organization and its leaders to position the organization to claim attorney-client communication and work product evidence protections to protect sensitive communications and analysis that are likely to emerge in the process.
Organizations seeking to preserve attorney-client privilege or work-product protection for post-incident assessments should engage qualified legal counsel before the assessment begins, define the legal purpose in writing, and carefully separate legal analysis from business and regulatory documentation that must be maintained in the ordinary course. Do not circulate preliminary findings broadly by email.
Boards and Senior Executives should:
- Direct management to deliver a written post-incident report and a forward-looking risk assessment of single-provider dependency, with a date certain.
- Record board or committee receipt, discussion, and direction in minutes; assign a responsible executive and require follow-up reporting.
- Decide, at the leadership level, the organization’s risk tolerance for loss of email and collaboration tools — how long the business can operate without them — and order, fund and monitor mitigation accordingly.
General Counsel, Compliance, and Privacy Officers should:
- Map which legal regimes apply ( e..g.HIPAA, GLBA/FTC, SEC/FINRA, NYDFS, ERISA, state law, GDPR/DORA/NIS2) and the documentation each requires.
- Inventory deadlines that fell during the outage — regulatory filings, plan notices, claims decisions, court and agency deadlines, contractual notices — and cure or document each.
- Issue a preservation notice for outage-related records, including logs, communications, and decisions made on alternate channels.
- Consider structuring the assessment under counsel’s direction for the purpose of legal advice; recognize that documentation regulators require must exist regardless of privilege and that courts have refused to shield incident reports prepared for business and regulatory purposes. In re Capital One Consumer Data Sec. Breach Litig., No. 1:19-md-2915, ECF No. 490 (E.D. Va. May 26, 2020), aff’d, 2020 WL 3470261 (E.D. Va. June 25, 2020).
- Evaluate Microsoft service contract and other service and insurance protections and requirements, capture and document relevant evidence, and provide timely written notice and claims.
CIOs, CISOs, and IT Leadership should:
- Document what failed, for how long, which business processes stopped, which workarounds were used, and which worked.
- Complete or update an applications and data criticality analysis and assign recovery time and recovery point objectives to each critical function.
- Evaluate out-of-band alternatives: secondary email and messaging, off-platform contact trees, locally cached or independently backed-up critical records, and break-glass administrative access that does not depend on the impaired service.
- Test the revised plan with a tabletop exercise simulating a multi-day loss of the primary productivity platform; document results and remediation.
HR and Payroll should:
- Reconstruct hours worked during the outage and pay engaged-to-wait time; do not dock exempt salaries for employer-caused downtime.
- Confirm payroll, benefits enrollment, leave administration, and time-off requests submitted during the outage were captured.
- Work with their organization’s information technology team and legal counsel to develop, implement and communicate an emergency workforce communication channel independent of corporate email and Teams, which fulfills applicable data privacy and security, Recordkeeping and other legal and operational parameters.
Plan Sponsors, Fiduciaries, and Benefit Administrators should:
- Obtain written incident reports from Microsoft, recordkeepers, TPAs, PBMs, and other service providers on how the outage affected plan operations.
- Verify delivery of electronically furnished disclosures and timeliness of claims, appeals, and COBRA communications during the outage window.
- Document the fiduciary review and add continuity and resiliency questions to the next service provider monitoring cycle.
- Ensure documented investigations, risk analysis and corrective action required by HIPAA is performed by the health plan and its business associates,
Healthcare Covered Entities and Business Associates should:
- Treat the event as a contingency-plan activation: document what was activated, emergency-mode operations used, and restoration timelines.
- Update the HIPAA risk analysis and risk management plan to reflect the event and retain the documentation for six years.
- Benchmark restoration against the proposed 72-hour standard and review business associate agreements for continuity and notice terms.
- Take corrective action and notifications as necessary to fulfill HIPAA requirements.
Public Companies and Regulated Financial Firms should:
- Evaluate disclosure obligations and the accuracy of existing Item 1C and risk-factor disclosures in light of what occurred.
- Confirm disclosure controls functioned while primary channels were impaired.
- Review BCP, Regulation S-P, Regulation SCI, and NYDFS obligations and any required regulator notices or plan updates.
- Consider the necessity or advisability of other actions, disclosures or risk mitigation actions.
Risk Management and Insurance should:
- Quantify losses, give timely notice to carriers, and calendar Microsoft SLA credit claim deadlines.
- Reassess coverage for dependent-business and non-malicious system-failure events at renewal.
Looking Ahead
Yesterday’s outage follows a run of large-scale technology failures in recent years affecting cloud, security software, and telecommunications providers. Regulators, plaintiffs, and insurers increasingly treat these events as foreseeable. Organizations that can show a documented, current assessment of their dependency on critical providers — and concrete steps taken to reduce it — will be far better positioned when the next disruption occurs than those that simply waited for service to come back.
For More Information
We hope this update is helpful. For more information about these or other legal, contractual or operational compliance or risk management, please contact the author, attorney Cynthia Marcotte Stamer via e-mail or via telephone at (214) 452-8297.
Solutions Law Press, Inc. invites you receive future updates by registering on our Solutions Law Press, Inc. Website and participating and contributing to the discussions in our Solutions Law Press, Inc. LinkedIn SLP Health Care Risk Management & Operations Group, HR & Benefits Update Compliance Group, and/or Coalition for Responsible Health Care Policy.
About the Author
Cynthia Marcotte Stamer is a practicing attorney board certified in labor and employment law by the Texas Board of Legal Specialization and management consultant, author, public policy advocate and lecturer widely known for her more than 35 years of health industry and other management work, public policy leadership and advocacy, coaching, teachings, and publications including leading edge work on data and systems, workforce and other risk management and compliance.
For decades she has advised business and governmental organizations, their boards and other leaders, employers, health plans, healthcare organizations, financial services businesses, technology developers and their vendors on managing data and technology compliance and risk, both in the U.S. and internationally. Her more than 35 years of experience on technology and data risk management spans health, workforce,and other IT development, innovation, deployment and risk management spans and includes advising, representing and defending clients on new and ongoing uses of data and technology. It also covers the design, documentation, implementation, audit and enforcement of policies, procedures, systems and safeguards, and the drafting and negotiation of data collection, analysis, automation and other systems agreements; breach and other event preparedness, investigation, response, and mitigation; legislative and regulatory affairs and other key legal and operational aspects of the design and use of technology in operations.
She frequently conducts board, executive and other briefings and training on cybersecurity, technology, and data, workforce and other legal and organizational risk management and compliance. A frequent speaker on cybersecurity and technology risk, she has spoken for the American Bar Association on “AI and Insurance,” HIPAA and a wide range of other data and technology topics, the ISSA Los Angeles Information Security Summit, ISSA-LA CISO Forum, and others on topics like “Shields Up: Cyber, AI & Other Technology Compliance & Risk Management Strategies To Strengthen Your Organization’s & Your Personal Data and Technology-Related Liability Defenses”. The long time scribe responsible for leading the ABA JCEB annual agency meeting with the HHS Office for Civil Rights, she also has frequently coordinated, moderated, and spoken along side Secret Service, FBI, Department of Justice, HHS OCR Deputy Directors and regional officials . She appeared as an invited witness before the U.S. Department of Labor’s ERISA Advisory Council in 2017.
Author of many highly regarded compliance, training and other resources on these and other operations, risk management, compliance and government affairs concerns including works on “HIPAA Privacy,” “E-Health and Technology Other Torts” published by the American Bar Association/Bureau of National Affairs, and many other works and training programs on health care, insurance and financial technology, data privacy and security. Her commentary has appeared in Healthcare Executive, Health Leaders, For The Record, Managed Healthcare Executive and Insurance Thought Leadership, and she shares thought leadership through her involvement with the ABA, ISSA and HIMSS, among others. She also publishes compliance updates through Solutions Law Press,
Ms. Stamer is widely recognized for her thought leadership and advocacy on these matters.
Ms. Stamer is peer recognized as a Martindale-Hubble “AV-Preeminent” (Top 1%) and “Top Rated Lawyer” with special recognition LexisNexis® Martindale-Hubbell® as “LEGAL LEADER™ Texas Top Rated Lawyer” in Health Care Law and Labor and Employment Law; as among the “Best Lawyers In Dallas” for her work in the fields of “Labor & Employment,” “Tax: ERISA & Employee Benefits,” “Health Care” and “Business and Commercial Law” by D Magazine, Cynthia Marcotte Stamer
For more information about Ms. Stamer or her health industry and other experience and involvements, see www.cynthiastamer.com or contact Ms. Stamer via telephone at (214) 452-8297 or via e-mail here.
About Solutions Law Press™
Solutions Law Press™ provides health care, human resources and employee benefit and other business risk management, legal compliance, management effectiveness and other coaching, tools and other resources, training and education on health care, leadership, governance, human resources, employee benefits, data security and privacy, insurance, and other key compliance, risk management, internal controls and operational concerns. If you find this of interest, you also be interested reviewing some of our other Solutions Law Press™ resources.
If you or someone else you know would like to receive future updates about developments on these and other concerns, please be sure that we have your current contact information including your preferred e-mail by creating your profile here.
NOTICE: These statements and materials are for general information and purposes only. They do not establish an attorney-client relationship, are not legal advice or an offer or commitment to provide legal advice, and do not serve as a substitute for legal advice. Readers are urged to engage competent legal counsel for consultation and representation considering the specific facts and circumstances presented in their unique circumstance at the particular time. No comment or statement in this publication is to be construed as legal advice or admission. The author reserves the right to qualify or retract any of these statements at any time. Likewise, the content is not tailored to any particular situation and does not necessarily address all relevant issues. Because the law constantly and often evolves, subsequent developments that could impact the currency and completeness of this discussion are likely. The author and Solutions Law Press, Inc. disclaim and have no responsibility to provide any update or otherwise notify anyone of any fact or law specific nuance, change, limitation, or other condition that might affect the suitability of reliance upon these materials or information otherwise conveyed in connection with this program. Readers may not rely upon, are solely responsible for, and assume the risk and all liabilities resulting from their use of this publication.
Circular 230 Compliance. The following disclaimer is included to ensure that we comply with U.S. Treasury Department Regulations. Any statements contained herein are not intended or written by the writer to be used, and nothing contained herein can be used by you or any other person, for the purpose of (1) avoiding penalties that may be imposed under federal tax law, or (2) promoting, marketing or recommending to another party any tax-related transaction or matter addressed herein.
©2026 Cynthia Marcotte Stamer. Non-exclusive right to republish granted to Solutions Law Press, Inc.™ For information about republication, please contact the author directly. All other rights reserved.