Skip to content

"Export restrictions on cryptography" doesn't explain the process if an ECCN is needed #3068

Open
@kyanha

Description

@kyanha

https://github.com/MicrosoftDocs/windows-uwp/blob/df14e7768acdb243190e3418db5afa5d65c5ff88/windows-apps-src/security/export-restrictions-on-cryptography.md

Regardless of the pointers this page has to the EAR and where to get an ECCN, there is no path forward documented once the EAR jurisdiction is identified. Once the ECCN is obtained, and compliance obligations established (does Microsoft do the necessary annual or semi-annual reporting, since it has first-hand knowledge of distribution from its store? Or is that still the obligation of the app developer, based on reporting it receives from Microsoft?), what is the next step in the approval process to get it listed on the Store?

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions