Subscriber Agreement Assignment: 30 Days' Notice—Assign or Retain?

This guide covers whether a Mighty Media LLC shared subscriber account can be assigned to a new owner, turning on the Assignment clause in the signed terms.

It gives the retain-by-default rule, the 30-day written notice threshold, and the verbatim clause check to run before any transfer request.

How Assignment Clauses Actually Work

An assignment clause is a term inside the signed subscriber agreement itself — the contract between the subscriber and the publisher. It answers one narrow question: can the rights and obligations under that contract move from the current subscriber to a different person or entity? That is a contract-law question, and it is resolved by reading the clause the parties actually signed. It is not the same act as reassigning a seat inside an administrative tool, and the two should never be treated as interchangeable when an ownership transfer request arrives.

The mechanism check is straightforward. Pull the signed agreement, find the Assignment clause, and read it verbatim. If the clause permits assignment only with prior written notice, then the transfer path runs through that notice — not through a portal, not through an email to support, and not through a verbal understanding. If the clause prohibits assignment or conditions it on publisher consent, then the default outcome is retention: the account stays with the current owner until the publisher agrees otherwise. The clause controls; everything else is administration.

The named counter-example is Microsoft's Visual Studio Subscriptions Admin Portal. Per Microsoft Learn's documentation on assigning subscriptions, administrators sign in to the portal, select Add, and then select Individual subscriber to assign a subscription to a single user. The same documentation describes assigning subscriptions one at a time, uploading subscriber information through the Bulk add feature, and — for organizations using Microsoft Entra ID — assigning subscriptions by using Microsoft Entra groups. Those are real, documented operations. They are also admin seat management: they move a license or benefit from one user record to another inside Microsoft's tooling. They do not transfer the underlying subscriber contract, and they do not satisfy an assignment clause in a separate signed agreement.

That distinction is the whole section. A portal operation changes who holds a seat. A contract assignment changes who holds the contract. If your signed terms require written notice before assignment, a portal reassignment performed without that notice leaves the contract where it was — with the original subscriber — no matter how clean the admin screen looks afterward.

So the practical rule for any ownership transfer request is a sequence, not a judgment call. First, locate the Assignment clause in the current signed terms and quote it. Second, classify what the requester is actually asking for: a contract transfer or a seat change. Third, if the clause requires written notice, send that notice in writing and calendar the notice period from the date of sending. Only after the notice condition is met does the assignment question move forward; until then, retain the account by default.

The Evidence: Verify, Don't Assume the Clause

Here is the uncomfortable truth I keep coming back to: the "30 days' written notice" figure that circulates in subscriber-transfer conversations has no published source behind it. Microsoft Learn documents Visual Studio subscription assignment in detail — individual adds, bulk upload, Microsoft Entra group flows, configurable notification emails — and nowhere in that documentation is a notice period stated. Justia's docket for Strike 3 Holdings v. Doe shows assignment as a formal, recorded court event (Filing 6, notice of assignment to District Judge Terry J. Hatter, Jr. and Magistrate Judge Sheri Pym), not a notice window. Neither source publishes a 30-day rule. So before anyone at Mighty Media LLC sends a transfer request built on that number, the only honest move is to pull the signed agreement copy and read the Assignment clause verbatim.

The check is mechanical, and it takes minutes. Retrieve the executed agreement — not a marketing page, not a summary, the signed document. Locate the Assignment clause. Read it word for word. If it specifies a notice period, that number governs, whatever folklore says. If it is silent on notice, the clause's other conditions (consent required, transfer prohibited, automatic on change of control) control instead. If the clause is ambiguous, that ambiguity is itself a finding: it means the transfer decision needs a legal read, not an operational guess.

Why does vendor documentation matter here? Because it proves assignment mechanics are vendor-specific and live in admin channels, not universal rules. Microsoft's Admin portal handles subscription assignment with three distinct flows and lets administrators configure who receives notification emails — a design that would be unnecessary if a single industry-standard notice period existed. Treat every publisher the same way: the operative assignment terms are wherever that vendor documents or contracts them, and the signed agreement is the anchor document.

One more discipline point: the 30-day figure is not just unverified — it is unverifiable from public grounding, which makes repeating it a liability. If your signed agreement does state a notice period, calendar the deadline the day you send written notice, and send it in the form the clause requires. If it states none, do not import one. The clause you signed is the only notice period that exists for your account.

Assign vs. Retain: The Comparison

Every transfer question collapses into two paths, and only one of them is yours to choose freely. Path A is retain: the subscription stays under the original account holder, and you make the changes that matter at the admin level — swap the sign-in email, redirect the billing contact, and set a different notification email for receiving communication, exactly the pattern Microsoft documents in the Visual Studio subscriptions admin portal. Terms continuity survives intact because the contract never moved. Path B is assign: a genuine contract assignment, attempted only if the clause in the signed agreement permits it, modeled on the documented pattern in Justia's Notice of Assignment filings, where the notice names its recipients specifically — a district judge and a magistrate judge, by name, on the record.

Run the comparison on four checks: does the account keep its history, does the counterparty have to agree, what paperwork does the path generate, and what happens if you get it wrong. Path A scores cleanly on the first three — history preserved, no counterparty consent needed beyond your own admin credentials, paperwork limited to your internal change log. Its weakness is the fourth: the legal relationship still points at the original subscriber, so anyone relying on the subscription is trusting that person's standing. Path B inverts this — it fixes the standing problem but requires the publisher's cooperation and creates a document trail that must be right the first time.

For a small media-operations portfolio, the winner is not close. Retain is the default because it is reversible, cheap, and requires nothing from the publisher. Assign is the exception you earn your way into: pull the signed agreement, read the assignment clause verbatim, and only if it expressly allows transfer — with whatever written-notice mechanics it specifies — do you draft the notice to a named recipient and send it in a verifiable form.

One guardrail ties the table together. If the clause is silent or ambiguous, Path B is off the table until you have the publisher's written confirmation of what notice it requires. An admin-side change can be undone in an afternoon; a botched assignment is a void transfer you may not discover until the moment you need the subscription most.

Costs and What Breaks Both Ways

Being wrong in either direction has a price, and the two prices are not symmetrical. If you attempt an assignment without clause authority, the transfer can be void — the new owner never validly holds the subscription, and you are pushed into a cancellation-and-resign flow. That flow costs you the account history attached to the original subscriber record and forces re-verification of the subscriber under whatever terms version is current at the time of re-signing. In operational terms, that is the worst outcome on the board: you lose continuity and you pay staff time twice, once to unwind the void transfer and once to onboard the replacement.

If you wrongly retain — declining a handoff that the clause actually permits — the damage is smaller and measurable. You delay a legitimate transfer by one notice cycle. Where the clause requires 30 days' written notice, that notice period is your delay ceiling, and it is the number to confirm in your own signed copy rather than assume. One cycle of delay is recoverable; a void transfer is not, because the history does not come back when you re-sign.

Budget the administrative cost of every assignment attempt, not just the successful ones. Each attempt consumes staff time to pull the signed agreement, locate the Assignment clause verbatim, draft and send written notice where required, calendar the notice deadline, and confirm the counterparty received it. Microsoft Learn documents the parallel administrative surface on the platform side: in the Visual Studio Subscriptions Admin portal, administrators add subscribers individually or through the Bulk add feature, and can assign by Microsoft Entra group where the organization uses Entra ID (Microsoft Learn, "Assign Visual Studio Subscriptions to users"). None of that portal work substitutes for clause authority — it is the mechanical step that follows a valid decision, not the decision itself.

Here is the comparison that should drive the operating rule:

The asymmetry is the whole argument for retaining by default. A declined-but-assignable transfer costs you one notice cycle; a void transfer costs you the account's continuity plus a full re-verification. So the rule is: retain unless the signed clause expressly permits the assignment, and only then attempt it. Before any transfer request, pull the signed agreement, read the Assignment clause verbatim, and if it calls for 30 days' written notice, send that notice in writing and calendar the deadline. Verify the notice figure against each signed agreement rather than relying on the circulating number — the available sources offers no published notice period, so the clause text is the only authority you have.

And Decision Rules

When the clause requires prior written consent, the operating sequence is short and mechanical. Step one: pull the signed agreement and copy the Assignment clause verbatim into the case file. Step two: send the written consent request to the publisher contact named in the agreement, and log the send date. Step three: calendar a response deadline of send date plus whatever notice period the clause itself states — the sources cited here publish no universal notice period, so the deadline must be read from your own clause text, not assumed. If no objection has been documented in writing by that deadline, record the retention decision and keep the account active under the current owner.

Use the Assignment Notice Worksheet below as the copy-usable artifact for every transfer request. Fill it in before you touch any admin portal, because the worksheet is what proves you checked the contract rather than assumed the answer.

Four if/then rules apply once the clause has been read verbatim. If the clause is silent on assignment, then retain the account by default and do not attempt a transfer. If the clause requires prior written consent, then send the notice in writing and calendar the response deadline before taking any further step. If the deadline passes with no documented objection, then log the retention decision and keep the account with the current owner. If the clause permits assignment without consent, then proceed with the transfer and still record the clause version date so the file shows which terms governed the decision.

The worksheet and the four rules exist because the decision hinges entirely on the clause in your current signed terms. Microsoft Learn documents how administrators assign Visual Studio subscriptions through the admin portal, including adding an individual subscriber and entering the sign-in email, but that portal workflow is an administrative action, not a contract term. The portal tells you how to move a seat; the signed agreement tells you whether you may. Pull the agreement first, copy the clause verbatim, and let the worksheet drive the decision.

What to do next

Frequently Asked Questions

What is the default handling of a Mighty Media LLC shared subscriber account?

Retain the subscriber account by default, and attempt assignment only when the signed agreement's Assignment clause expressly permits it.

When must written notice be sent if the Assignment clause requires it?

Send that notice in writing before any ownership transfer request.

What condition must be met before proceeding with an assignment attempt?

The threshold condition named in the reader rule for proceeding with an assignment attempt must be met.

What follow-up action is specified after the written notice is sent?

Calendar the 3-day follow-up after sending the notice.

What must be done with the signed agreement before any ownership transfer request?

Pull the signed agreement copy and locate the Assignment clause verbatim.

What form of clause review is required before a transfer request?

Read the Assignment clause verbatim in the signed agreement copy, not a summary or template.

Quick answers