Mich. Comp. Laws § § 125.403
Repealed. 1972, Act 230, Eff. Jan. 1, 1973.
Operative Text
Repealed. 1972, Act 230, Eff. Jan. 1, 1973.
MCL § 125.403 was formally repealed by Michigan Act 230 of 1972, with the repeal taking effect on January 1, 1973. As of that date, this provision no longer carries any legal force or imposes any requirements, prohibitions, or permissions under Michigan law. Any rules or standards that may have existed under this section were extinguished upon the effective date of repeal.
Plain English — not legal advice.
Because MCL § 125.403 was repealed effective January 1, 1973, property owners and managers should not rely on this section as a source of rights, obligations, or authority. Compliant operators look to currently active Michigan statutes and local ordinances when determining their responsibilities. Consulting the broader MCL § 125.401 et seq. framework and its successor provisions is the appropriate starting point for identifying applicable housing regulations.
General guidance for property managers — not legal advice for your specific situation. Consult an attorney for advice on your case.
MCL § 125.403 has been repealed since January 1, 1973, meaning it no longer provides any enforceable tenant protections or landlord obligations. Tenants seeking applicable housing rights in Michigan should look to currently active statutes and local ordinances rather than this section. Tenant-rights organizations and legal aid resources can help identify which current provisions may be relevant to a given housing situation.
General guidance for tenants — not legal advice for your specific situation. Consult a tenant-rights organization or attorney for advice on your case.
Generated October 13, 2026 — auto-generated, not yet human-reviewed. See /transparency for methodology.
Effective Timeline
References Out
No outbound references recorded yet for this provision.
References In
Rules and statutes that cite this regulation
Related Rules
Source Information
Use this in your app
Access this data programmatically via our API