BIS Remote Access Rule Can Require Licenses After Lawful Chip Delivery · Traverse Analysis
BIS Remote Access Rule Can Require Licenses After Lawful Chip Delivery
BIS's new remote access rule can require a data center to obtain authorization for a later use of chips it received lawfully without an export license. The supplier's notice assigns responsibility for that decision.
An overseas data center can receive chips lawfully without a BIS license and still need authorization for a later customer use. The remote access rule BIS released on November 16 assigns responsibility for that later decision. For certain transactions after Federal Register publication, the supplier must notify the recipient that a covered change in use requires authorization. The operator making that change must obtain it.
The new end use control applies to transactions made with knowledge that specified EAR items are destined for a data center providing or planning to provide access to more than 12,000,000 aggregate TPP at one data center or across linked centers, to or for companies headquartered in Macau or an EAR arms embargo destination, or with an ultimate parent headquartered there. It turns an allocation of computing power into a potential licensing event even when the equipment stays in place. The rule's concurrent rescission of the AI Diffusion framework leaves that constraint intact.
For the operator's export compliance manager, the immediate task is to identify which proposed allocations need a fresh authorization decision. The , with the date still blank. Publication had not been confirmed as of November 16. The duties discussed here describe that text, not a verified commencement date.
The notice assigns responsibility for the later use
Section 744.24(e) addresses a narrow category. The export, reexport or transfer must occur on or after publication without authorization because the sender has no knowledge of a prohibited use under the section and no other EAR license requirement applies.
For those transactions, the sender must inform the recipient that a subsequent use meeting the remote access conditions requires BIS authorization. The notice must specify that the transferor, such as the data center operator, must obtain that authorization and follow the EAR's customer diligence guidance. Aggregate TPP sums the defined processing performance of the specified chips or commodities. The linked-center definition covers infrastructure allowing facilities to share resources, balance workloads and replicate data as a unified whole, including digital links.
This division addresses an information gap. A supplier knows the basis on which it delivered the equipment. The operator decides what access to sell later. Paragraph (e) requires the first party to warn the second that the basis for proceeding without authorization may no longer hold for the next use.
Consider a hypothetical operator receiving covered equipment after publication for uses that require no authorization under any applicable EAR provision. Later, it proposes giving a company whose ultimate parent is headquartered in China access above the threshold across linked sites. On those assumptions, the original delivery remains lawful. The proposed use creates the next licensing question.
Traverse's earlier analysis of H200 licenses and market access followed the gap between permission to ship and usable customer capacity. Under the new notification provision, there may be no original license to consult. The operator has to preserve why authorization was unnecessary then and determine whether the proposed use changes that conclusion.
Transfer on or after publication without authorization, with no prohibited use known and no other license requirement
Paragraph (e) requires notice to the recipient. The party making a later covered change in use must obtain authorization.
Equipment originally delivered under a license, or lawfully without one before publication
Paragraph (e)'s notification category does not fit that original delivery. Review any license and the controls applicable to the proposed use.
Data center already supplying significant compute to the covered companies before publication
Paragraph (b)(3) requires a license within 90 days of effectiveness to continue those services, or the operator faces future export restrictions.
The third row requires obtaining a license. Filing an application alone does not meet the text. Nor does this provision establish a general 90-day grace period for every new allocation. Its publication and effectiveness references must be resolved against the eventual Federal Register record before assigning a calendar deadline.
An exception to one control does not clear the customer
Paragraph (e) assumes no other EAR license requirement applies. That condition matters because this rule does not replace every other route to licensing.
For example, the exclusion for qualifying recipients headquartered in the United States or with a US ultimate parent concerns the destination license requirement for Indonesia, Malaysia, Singapore, Thailand and Brazil, and depends on reporting. It does not remove the remote access end use control. A qualifying equipment recipient and a covered compute customer can sit on opposite sides of the same transaction.
The processing threshold is equally easy to overread. BIS separately explains that section 744.23 can reach equipment supplied for a covered entity, including when that entity is the direct or indirect purchaser or the exclusive or primary remote user of the data center's compute. Primary means more than half of total compute in that explanation. Staying below 12,000,000 aggregate TPP does not establish that no EAR license is needed.
Even the new commercial recommender exclusion has a limited reach. It requires exclusive design and use for recommendation, excludes systems incorporating generative models, and requires submission of the specified company, processing performance and diligence information. It does not exempt a transaction from the separate section 744.23 control.
The commercial question is what can be promised next
Paragraph (e) gives operators a reason to revisit how equipment records support customer commitments. A notice of future licensing duties is not an authorization to deliver the future service. BIS also adds the new control to the EAR recordkeeping provisions, expressly connecting the notice and authorization requirements to retained records.
Operators should connect that notice and the original basis for proceeding without authorization to the allocation approval record. The proposed customer's headquarters and ultimate parent, the processing performance that customer would be able to access across linked facilities and the intended use determine whether the proposed use needs BIS authorization. The rule's diligence provisions also expect information sufficient to check the foreign data center's customers, making an unresolved refusal to provide it a presumptive knowledge red flag.
Publication in the Federal Register will fix the start date and reveal any changes to the posted text. Operators can prepare the allocation record now, but should not date the 90-day deadline from the announcement or treat a planned license application as permission to begin a covered service.
Daily Trade Brief
Get the next one in your inbox.
New U.S. trade actions and the analysis that changes an import, customs, or counsel file, on weekday mornings after you confirm your address.
From reading to review
Run the numbers on your lane.
The duty calculator runs the current stack for any HTS code and origin. A free account opens full tool output, AD/CVD detail, Chapter 98 processing, and available exports.