Tenant Tech, Landlord Problem: Managing Tenant-Owned Devices in Commercial Buildings

When Tenant Convenience Becomes a Building Problem

This episode of Built, Wired & Secured opens with a sharp example of how a seemingly isolated tenant device can trigger a much broader operational failure. A tenant-owned PoE switch fails two floors away, access readers go dark, lobby doors lock, and the building cafe loses payment capability. What looked like one tenant install became a shared building emergency.

Alex Morgan is joined by Michael Harrington and James Rogers to break down why tenant-owned technology has become a growing challenge inside commercial buildings. The conversation focuses on the devices tenants increasingly bring into their spaces: smart sensors, cameras, access devices, PoE equipment, and other network-connected gear that may appear minor on install day but can create outsized risk when they touch shared infrastructure.

The Core Question: What Breaks If This Goes Down?

Michael centers the discussion on one question: what breaks if this goes down? That framing exposes the real problem. Ownership may be fuzzy on paper, but dependencies are very real in practice. A tenant may say the device is theirs. A building owner may say it is not on their bill. But when that device touches shared power, shared network paths, common closets, common area services, or life-safety-adjacent systems, building operations inherits the outage whether it planned for it or not.

The panel explains that this is where single points of failure hide. If nobody has documented the breaker, labeled the cabling path, identified the switch, or stocked a spare, the operations team is left troubleshooting blind during a live incident.

• Shared dependencies create shared risk, even when device ownership is private.
• Unapproved installs often leave behind no documentation, no spares, and no accountability.
• At outage time, the building team becomes the default responder.

Why Tenant-Owned Tech Slips In Unchecked

The episode makes clear that these problems are not always caused by bad intent. Speed is a major driver. Tenants want something live tomorrow. Vendors market turnkey installs that feel self-contained. And many people assume low risk because the device seems small or routine. As James notes, those assumptions cause teams to skip verification steps that would have caught conflicts in power, networking, and maintenance responsibility.

The result is an environment where hidden dependencies accumulate over time. One example in the conversation involves three PoE cameras on a single switch fed by a UPS that was not sized for the total load. When the UPS tripped, back-of-house lighting went dark. The lesson is straightforward: network-connected devices are not just IT issues. They are operational, electrical, and facilities issues too.

Where Building Oversight Should Start

Michael draws a practical boundary. If a device touches shared infrastructure, common power, shared closets, life safety, or common area services, the building needs visibility and approval. If the technology is truly contained on tenant-dedicated circuits and a private network with no shared dependencies, tenants can have more latitude.

The key phrase is visibility before the fact. The panel is not arguing for heavy bureaucracy. They are arguing against surprises.

• Shared closets require oversight.
• Shared power paths require oversight.
• Interfaces with building systems require oversight.
• Private, isolated tenant systems can move faster when they stay truly isolated.

The Lightweight Governance Model That Actually Works

Rather than build a slow approval process, James describes a lightweight approach that balances tenant autonomy with operational control. Their model includes device registration, a one-page checklist, and a brief 30-minute verification at install. The point is to make the safe path easier than the risky path.

The one-page checklist captures the details that prevent hours of troubleshooting later:

• Device model and vendor contact
• Power source and breaker ID
• Physical location
• Cabling path
• UPS requirement
• Whether the device interfaces with building systems
• Whether the vendor needs admin-level credentials

If admin credentials are required, the review escalates. During verification, a technician confirms labels, circuit IDs, and that the device is placed on a tenant VLAN or physically separate circuit. As the discussion points out, labeling the circuit and VLAN is not paperwork for paperwork’s sake. It is what makes later troubleshooting possible.

Why Segmentation Alone Is Not Enough

One of the strongest operational points in the episode is that network segmentation helps, but it does not solve everything. Segmentation may reduce network blast radius, but it does not fix power design problems, physical placement issues, or uncontrolled cabinet access. That is why the panel recommends pairing technical controls with physical rules.

A practical example: no tenant gear in common cabinets unless it is installed in a monitored, designated bay. The team also describes using designated tenant racks with capped power budgets and requiring a spare parts declaration. If tenants needed more capacity or support, they either supplied spares or signed a service SLA.

This pairing of logical and physical controls is a recurring theme in the episode. A stable building environment depends on both.

Enforcement, Incentives, and the Reality of Contractor Behavior

The conversation does not pretend every contractor will cooperate. James acknowledges that some try to skirt the rules when timelines are tight. In cases where cooperation fails, the team may place a hold on the space until remediation occurs. It is unpopular, but it prevents repeat outages.

At the same time, the episode emphasizes that tone matters. Rather than frame registration as policing, the team encourages positioning it as protection for tenant uptime. Offering a free 30-minute verification helps tenants see the process as value, not friction.

• Rigid rules alone can drive installs underground.
• Fast, simple verification keeps tenants engaged.
• Consistency and clarity matter more than scale.

Operational Wins That Reduced Outages

Several practical wins stand out. One was adding monitored power metering in shared closets. That gave the team visibility into unexpected loads and let them contact tenants before failures occurred. Another was a “bring your gear” packet that included label stickers, a circuit log template, and an intake email. Vendors who arrived with that packet completed cleaner installs and generated fewer follow-up incidents.

Just as valuable are the failures the panel shares openly. Trying to ban tenant devices outright pushed installs underground and made the problem worse. Overly rigid rules that slow move-ins cause people to bypass operations entirely, which removes visibility and control.

The Five-Step Checklist to Use This Week

The episode closes with a practical checklist facilities and property teams can act on immediately:

• Create a one-page device registration checklist.
• Require a brief on-site verification during install.
• Define where tenant gear can and cannot sit physically.
• Plan for power capacity and documented spares.
• Use network segmentation paired with physical controls.

The guests add two more principles worth carrying forward: document the process in tenant onboarding, and train a small group to perform verifications consistently. In their words, consistency beats scale.

Final Takeaway

This episode is ultimately about governance that is practical, not heavy-handed. Tenant-owned technology is not going away. The goal is not to stop it. The goal is to make it visible, contained, and supportable before it becomes a building-wide outage. Small habits like labels, spares, circuit logs, and a short verification window can prevent late-night emergencies and protect both tenant flexibility and building resilience.

Tenant-Owned Technology Is Becoming a Building Operations Issue

Commercial buildings are seeing more tenant-owned technology than ever before. Smart sensors, PoE switches, cameras, networked AV, and other connected devices often arrive as part of a tenant improvement, a vendor installation, or a quick operational upgrade. On the surface, many of these installs look small and self-contained. In reality, they can create shared operational risk for the entire property.

That is the central message in this episode of Built, Wired & Secured, where Alex Morgan speaks with Michael Harrington and James Rogers about how tenant-owned technology quietly shifts responsibility, risk, and recovery burden onto building owners and operators.

The discussion starts with a vivid failure scenario: a tenant’s PoE switch fails two floors away, access readers go dark, lobby doors lock, and the building cafe cannot process payments. The building operations team spends the morning tracing a device it never approved. That story captures the problem perfectly. A local install became a building-wide incident because the underlying dependencies were shared, undocumented, and poorly governed.

The Hidden Risk Is Not Ownership. It Is Dependency.

One of the most useful ideas in the conversation is the question Michael asks: what breaks if this goes down? That question cuts through a lot of the confusion around ownership. A tenant may own the device. The landlord may not pay the bill for it. But if that device depends on shared power, shared network paths, common cabinets, or common area services, the building inherits the impact when something fails.

That is where tenant technology becomes a landlord problem. The issue is not simply who purchased the device. The issue is whether the device sits on infrastructure that other people depend on. If it does, then the operational blast radius extends far beyond the tenant suite.

In practice, these situations often create hidden single points of failure:

• A tenant device shares a switch or UPS with building-critical systems.
• A contractor places gear in a common closet without clear labeling.
• No one documents the breaker, cabling path, or support contact.
• No spare equipment is available when failure occurs.

When the outage happens at 2:00 a.m., the operations team is left guessing which device failed, which circuit feeds it, and who is supposed to respond.

Why These Installations Keep Happening

The episode does a good job of treating the root cause realistically. Most of these problems do not start with malicious intent. They start with speed. Tenants want something live tomorrow. Vendors sell turnkey deployments that sound simple. And decision-makers assume a small sensor or camera has limited consequence.

Those assumptions remove the very checks that would have caught the risk early. If nobody verifies power load, network segmentation, physical placement, or building-system interfaces, the install moves forward with hidden dependencies intact.

James shares an example that makes this concrete: three PoE cameras were placed on one switch feeding a UPS that was not sized for the combined load. The UPS tripped, and back-of-house lighting went dark. That is an important reminder for property teams. Tenant technology is not just an IT concern. It intersects with facilities, electrical planning, maintenance, and life-cycle support.

Where Oversight Should Begin

Michael offers a clear line that building teams can use immediately. If a device touches shared infrastructure, common power, shared closets, life safety, or common area services, the building needs visibility and approval. If the device is fully contained on tenant-dedicated circuits and a private network with no shared dependencies, there is more room to let tenants move quickly.

This is a practical standard because it is based on operational exposure, not bureaucracy. The goal is not to slow down every installation. The goal is to prevent surprises in environments where a single undocumented decision can impact multiple occupants.

That principle matters for commercial real estate technology strategy. Buildings work best when infrastructure decisions are governed according to risk domain. If the install stays inside a tenant’s isolated environment, flexibility can stay high. If it touches common systems, visibility has to increase.

The Best Control Is Often a Lightweight One

A major takeaway from the episode is that governance does not need to be heavy to be effective. James describes a lightweight process built around device registration, a one-page checklist, and a 30-minute on-site verification at install. That combination gives operators enough structure to catch the majority of avoidable problems without turning every tenant request into a long approval cycle.

The one-page checklist includes the details that matter most operationally:

• Device model and vendor contact
• Power source and breaker ID
• Physical location
• Cabling path
• UPS requirement
• Whether the device interfaces with building systems
• Whether the vendor requires admin-level credentials

If administrative credentials are involved, the review escalates. Otherwise, a technician performs a short verification to confirm labels, circuit IDs, and that the device sits on a tenant VLAN or physically separate circuit. That may sound simple, but simple is exactly the point. The panel repeatedly argues for controls that are easy enough to follow consistently.

Segmentation Helps, but Physical Rules Matter Too

Another strong insight from the episode is that network segmentation is necessary but incomplete. Segmentation can reduce the impact of network misconfiguration or compromise, but it does not address power planning, cabinet access, or equipment placement. A device can still be badly installed even if it is on the right VLAN.

That is why the discussion emphasizes pairing logical controls with physical controls. One example is a rule against placing tenant gear in common cabinets unless it is installed in a designated, monitored bay. Another is the use of designated tenant racks with capped power budgets and mandatory spare-part declarations.

This approach does two things. First, it limits the blast radius of poor tenant decisions. Second, it makes responsibility more visible. When a device sits in a defined location with documented power and support expectations, the building can respond faster and with less confusion.

Good Policy Needs Good Framing

The episode also addresses a real-world tension: some tenants and contractors view mandatory registration as policing. James is candid that not everyone cooperates when timelines are tight. In some cases, operations may need to place a hold on a space until remediation occurs. That is not ideal, but it can be necessary to stop recurring outages.

Still, the broader recommendation is to lead with incentives rather than confrontation. Offer a free 30-minute verification. Explain that the process exists to protect tenant uptime. Keep the checklist short. Make the safe path faster than the workaround. When people understand the process as operational protection rather than gatekeeping, compliance improves.

This is where experienced technology governance differs from generic rulemaking. The objective is not to win a policy argument. The objective is to keep the building reliable while preserving tenant flexibility wherever possible.

What Worked, and What Failed

The guests share several concrete improvements that reduced headaches. Monitored power metering in shared closets helped identify unexpected loads before failure. A “bring your gear” packet with label stickers, a circuit log template, and an intake email helped vendors arrive prepared and finish cleaner installs. A small notification workflow allowed teams to call tenants at the first sign of trouble rather than after a full outage.

They also highlight what did not work. Trying to ban tenant devices outright pushed installs underground. Overly rigid rules slowed move-ins and encouraged people to bypass operations. In both cases, the building lost visibility, which made the environment more fragile, not less.

What Property Teams Can Do This Week

The episode closes with a practical five-step checklist:

• Create a one-page device registration checklist.
• Require a brief on-site verification during install.
• Define where tenant gear can and cannot sit physically.
• Plan for power capacity and documented spares.
• Use network segmentation paired with physical controls.

Two final additions make that checklist stronger: fold the process into tenant onboarding, and train a small group to perform verifications consistently. Buildings do not become resilient through one-time policy statements. They become resilient through repeatable operating habits.

Why This Matters for Building Reliability

For owners, operators, and facilities leaders, the message is clear: tenant-owned technology is now part of the building risk picture. The right response is not to fight every install or overengineer a complex approval process. It is to create practical governance that makes tenant technology visible, contained, and supportable.

That is where a true Technology Partner adds value. Good governance is not just about saying no. It is about designing processes that protect uptime, reduce troubleshooting time, and preserve tenant flexibility without exposing shared infrastructure to unmanaged risk.

If this topic is familiar, the full episode is worth a listen. It offers a grounded operational framework property teams can apply immediately, with no jargon and no unnecessary complexity. Small habits such as labeling, documenting circuits, validating power, and stocking spares can prevent the kind of outage that disrupts tenants, damages confidence, and consumes an entire morning of building operations.

Listen to the episode for the full conversation and use it as a practical starting point for better tenant tech governance in your building.