Add wildcard entries for web.core.windows.net and web.core.usgovcloudapi.net

[macros82]

Public Suffix List (PSL) Submission

Checklist of required steps

• Description of Organization
• Robust Reason for PSL Inclusion
• DNS verification via dig
• Each domain listed in the PRIVATE section has and shall maintain at least two years remaining on registration, and we shall keep the _psl TXT record in place in the respective zone(s).

Submitter affirms the following:

• We are listing any third-party limits that we seek to work around in our rationale such as those between IOS 14.5+ and Facebook (see Issue #1245 as a well-documented example)
• This request was not submitted with the objective of working around other third-party limits.
• The submitter acknowledges that it is their responsibility to maintain the domains within their section. This includes removing names which are no longer used, retaining the _psl DNS entry, and responding to e-mails to the supplied address. Failure to maintain entries may result in removal of individual entries or the entire section.
• The Guidelines were carefully read and understood, and this request conforms to them.
• The submission follows the guidelines on formatting and sorting.
• A role-based email address has been used and this inbox is actively monitored with a response time of no more than 30 days.

Abuse Contact:

• Abuse contact information (email or web form) is available and easily accessible.

Email Address: abuse@microsoft.com
URL where abuse contact or abuse reporting form can be found: https://msrc.microsoft.com/report/abuse

---

For PRIVATE section requests that are submitting entries for domains that match their organization website's primary domain, please understand that this can have impacts that may not match the desired outcome and take a long time to rollback, if at all.

To ensure that requested changes are entirely intentional, make sure that you read the affectation and propagation expectations, that you understand them, and confirm this understanding.

PR Rollbacks have lower priority, and the volunteers are unable to control when or if browsers or other parties using the PSL will refresh or update.

(Link: about propagation/expectations)

• Yes, I understand. I could break my organization's website cookies and cause other issues, and the rollback timing is acceptable. Proceed anyways.

---

Description of Organization

Microsoft Corporation is a global leader in technology, headquartered in the United States. Its cloud platform, Azure, ranks among the world’s top cloud service providers. Guided by its mission to empower every person and every organization on the planet to achieve more, Microsoft continues to drive innovation and transformation across industries.

Organization Website:
https://www.microsoft.com/

Reason for PSL Inclusion

Promoting these two suffixes to wildcards (*.web.core.windows.net, *.web.core.usgovcloudapi.net) makes each .z.web.core. its own registrable domain, giving every storage account a clean, independent origin boundary. The primary purpose is cookie / origin security isolation between independent customer tenants. This benefits every PSL consumer (browsers, cookie libraries, CORS and same-site logic, certificate scoping). This mirrors the wildcard-only multi-tenant pattern already present in the list (e.g. *.azurecontainer.io). The flat entries are already deployed and in effect, so this change tightens isolation without expanding namespace surface.

These are PRIVATE-section domains under Microsoft-owned registrations (windows.net, usgovcloudapi.net) on Microsoft's corporate registrar; we will maintain >1 year registration term and keep the _psl TXT records in place. We are not seeking to work around any third-party limit.

Number of users this request is being made to serve: Azure currently supports millions of users.

DNS Verification

[dnsguru]

@macros82 please advise once the _PSL TXT records are in place

Some approval factors to note:

• Known contributor, verified as team updater from submitting org, prior contributor.
• Correctly sorted

[simon-friedberger]

We previously merged these after only validating the org.
See #2700