[Excel] Release ExcelApi 1.20 to GA

[alison-mk]

ExcelApi 1.20 overview article.

The PR does not update the excel-api-requirement-sets.md table. That table will be udpated in a subsequent PR once those details are acquired.

[learn-build-service-prod]

Learn Build status updates of commit 4fc1882:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/docs-ref-autogen/common_preview/toc.yml	✅Succeeded	View (common-js-preview || outlook-js-preview || excel-js-preview || onenote-js-1.1 || powerpoint-js-preview || word-js-preview)
docs/docs-ref-autogen/common/toc.yml	✅Succeeded	View (>=common-js || >=outlook-js-1.1 || >=excel-js-1.1 || onenote-js-1.1 || >=powerpoint-js-1.1 || visio-js-1.1 || >=word-js-1.1) View (common-js || <outlook-js-preview || <excel-js-preview || <powerpoint-js-preview || <word-js-preview) View (common-js-preview || outlook-js-preview || excel-js-preview || onenote-js-1.1 || powerpoint-js-preview || word-js-preview)
docs/docs-ref-autogen/excel_1_1/toc.yml	✅Succeeded	View (excel-js-1.1)
docs/docs-ref-autogen/excel_1_10/toc.yml	✅Succeeded	View (excel-js-1.10)
docs/docs-ref-autogen/excel_1_11/toc.yml	✅Succeeded	View (excel-js-1.11)
docs/docs-ref-autogen/excel_1_12/toc.yml	✅Succeeded	View (excel-js-1.12)
docs/docs-ref-autogen/excel_1_13/toc.yml	✅Succeeded	View (excel-js-1.13)
docs/docs-ref-autogen/excel_1_14/toc.yml	✅Succeeded	View (excel-js-1.14)
docs/docs-ref-autogen/excel_1_15/toc.yml	✅Succeeded	View (excel-js-1.15)
docs/docs-ref-autogen/excel_1_16/excel/excel.cardlayout.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.cardlayoutsection.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.cellvalue.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.cellvalueandpropertymetadata.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.compactlayout.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.entitypropertytype.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.errorcellvalue.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.referencedvalue.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/toc.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_17/excel/excel.cardlayout.yml	✅Succeeded	View (excel-js-1.17)
docs/docs-ref-autogen/excel_1_17/excel/excel.cardlayoutsection.yml	✅Succeeded	View (excel-js-1.17)
docs/docs-ref-autogen/excel_1_17/excel/excel.cellvalue.yml	✅Succeeded	View (excel-js-1.17)
docs/docs-ref-autogen/excel_1_17/excel/excel.cellvalueandpropertymetadata.yml	✅Succeeded	View (excel-js-1.17)
docs/docs-ref-autogen/excel_1_17/excel/excel.compactlayout.yml	✅Succeeded	View (excel-js-1.17)
docs/docs-ref-autogen/excel_1_17/excel/excel.entitypropertytype.yml	✅Succeeded	View (excel-js-1.17)
docs/docs-ref-autogen/excel_1_17/excel/excel.errorcellvalue.yml	✅Succeeded	View (excel-js-1.17)

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.

[AlexJerabek]

Can you please remove these .js and .js.map files from the PR?

[learn-build-service-prod]

Learn Build status updates of commit ee10589:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/docs-ref-autogen/common_preview/toc.yml	✅Succeeded	View (common-js-preview || outlook-js-preview || excel-js-preview || onenote-js-1.1 || powerpoint-js-preview || word-js-preview)
docs/docs-ref-autogen/common/toc.yml	✅Succeeded	View (>=common-js || >=outlook-js-1.1 || >=excel-js-1.1 || onenote-js-1.1 || >=powerpoint-js-1.1 || visio-js-1.1 || >=word-js-1.1) View (common-js || <outlook-js-preview || <excel-js-preview || <powerpoint-js-preview || <word-js-preview) View (common-js-preview || outlook-js-preview || excel-js-preview || onenote-js-1.1 || powerpoint-js-preview || word-js-preview)
docs/docs-ref-autogen/excel_1_1/toc.yml	✅Succeeded	View (excel-js-1.1)
docs/docs-ref-autogen/excel_1_10/toc.yml	✅Succeeded	View (excel-js-1.10)
docs/docs-ref-autogen/excel_1_11/toc.yml	✅Succeeded	View (excel-js-1.11)
docs/docs-ref-autogen/excel_1_12/toc.yml	✅Succeeded	View (excel-js-1.12)
docs/docs-ref-autogen/excel_1_13/toc.yml	✅Succeeded	View (excel-js-1.13)
docs/docs-ref-autogen/excel_1_14/toc.yml	✅Succeeded	View (excel-js-1.14)
docs/docs-ref-autogen/excel_1_15/toc.yml	✅Succeeded	View (excel-js-1.15)
docs/docs-ref-autogen/excel_1_16/excel/excel.cardlayout.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.cardlayoutsection.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.cellvalue.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.cellvalueandpropertymetadata.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.compactlayout.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.entitypropertytype.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.errorcellvalue.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.referencedvalue.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/toc.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_17/excel/excel.cardlayout.yml	✅Succeeded	View (excel-js-1.17)
docs/docs-ref-autogen/excel_1_17/excel/excel.cardlayoutsection.yml	✅Succeeded	View (excel-js-1.17)
docs/docs-ref-autogen/excel_1_17/excel/excel.cellvalue.yml	✅Succeeded	View (excel-js-1.17)
docs/docs-ref-autogen/excel_1_17/excel/excel.cellvalueandpropertymetadata.yml	✅Succeeded	View (excel-js-1.17)
docs/docs-ref-autogen/excel_1_17/excel/excel.compactlayout.yml	✅Succeeded	View (excel-js-1.17)
docs/docs-ref-autogen/excel_1_17/excel/excel.entitypropertytype.yml	✅Succeeded	View (excel-js-1.17)
docs/docs-ref-autogen/excel_1_17/excel/excel.errorcellvalue.yml	✅Succeeded	View (excel-js-1.17)

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 issues. Other issues are also a high priority. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

#	File	Term	Line	Sev	AI Recommendation	Class	AI Review Details
1	generate-docs\api-extractor-inputs-excel-release\Excel_1_20\excel.d.ts	Metro	5726	2	Replacement required	Legal	Details The term `Metro` is used in the context of a file name or package label (e.g., 'the RichValueWebImageValue.xml file is missing from the Metro package'). In Microsoft documentation and code, `Metro` was previously used as a UI branding term, but it is now deprecated and should be replaced with the current, product-appropriate term to avoid confusion and potential sensitivity. In this context, it is not a person's name, a URL, a field name, or a forbidden term example, so it should be replaced according to the product team's guidelines.
2	generate-docs\api-extractor-inputs-excel-release\Excel_1_20\excel.d.ts	Metro	5740	2	No action needed	Legal	Details The term `Metro` is used in the context of a file or package name (RichValueRel.xml file is missing from the Metro package), not as a user-facing UI term or branding. According to the rules, terms in file paths or names do not need to be replaced.
3	generate-docs\api-extractor-inputs-excel-release\Excel_1_20\excel.d.ts	country	20032	2	Replacement required	Geopolitical	Details The term `country` is used as a value in the enum ChartMapAreaLevel, which is used to specify the mapping level for a region map chart. In this context, it is used to label a country/region level in a list of possible mapping levels. To avoid geopolitical issues and to be inclusive, it should be replaced with `country/region`.
4	generate-docs\api-extractor-inputs-excel-release\Excel_1_20\excel.d.ts	country	31861	2	Replacement required	Geopolitical	Details The term `country` is used as an enum value to label a region level in a chart series layout (specifically, ChartMapAreaLevel). To avoid geopolitical issues, it should be replaced with `country/region` or a similar neutral term.
5	generate-docs\api-extractor-inputs-excel-release\Excel_1_20\excel.d.ts	country	31861	2	Replacement required	Geopolitical	Details The term `country` is used as an enum value to represent a geographic region level in a chart API. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
6	generate-docs\api-extractor-inputs-excel-release\Excel_1_20\excel.d.ts	country	44702	2	Replacement required	Geopolitical	Details The term `country` is used in the context of an enum value for ChartMapAreaLevel, specifically as a value for mapping levels in region map charts. In Microsoft and industry guidance, when referring to a country in a UI, API, or as a selectable value, it should be replaced with `country/region` to avoid geopolitical issues and to be inclusive of regions that are not universally recognized as countries. Therefore, `country` should be replaced with `country/region` in this context.
7	generate-docs\api-extractor-inputs-excel-release\Excel_1_20\excel.d.ts	country	50739	2	Replacement required	Geopolitical	Details The term `country` is used as a value in the ChartMapAreaLevel enum, which is exposed to users as a label for a map level. To avoid geopolitical issues, it should be replaced with `country/region` or a similar neutral term.
8	docs\docs-ref-autogen\excel_1_20\excel\excel.interfaces.chartmapoptionsupdatedata.yml	country	48	2	No action needed	Geopolitical	Details The term `country` is used as a string literal value in an API property definition, specifically as an option for the `level` property in a TypeScript interface. In this context, it is a field/parameter value and part of a code contract, so it does not need to be replaced according to the exception for field or parameter names and values.
9	docs\docs-ref-autogen\excel_1_20\excel\excel.interfaces.chartmapoptionsupdatedata.yml	country	52	2	Replacement required	Geopolitical	Details The term `country` is used as a value in an enum for a property that specifies mapping levels in a region map chart. This is labeling a country/region list or similar resource, so to avoid geopolitical issues, it should be replaced with `country/region`.
10	docs\docs-ref-autogen\excel_1_20\excel\excel.fielderrorcellvaluesubtype.yml	Metro	31	2	No action needed	Legal	Details The term `Metro` is used here to refer to a package name or file path context, not as a user interface or branding term. According to the rules, terms in file paths or package names do not need to be replaced.
11	docs\docs-ref-autogen\excel_1_20\excel\excel.fielderrorcellvaluesubtype.yml	Metro	55	2	No action needed	Legal	Details The term `Metro` is used here to refer to a package name or file package in a technical context, not to the user interface of a Microsoft product. According to the rules, replacement is only required when referring to the UI, not for package or file names.
12	docs\docs-ref-autogen\excel_1_20\excel\excel.interfaces.chartmapoptionsdata.yml	country	48	2	No action needed	Geopolitical	Details The term `country` is used as a value in a code enum or parameter list, specifically as a mapping level in a chart API. According to the guidelines, when referring to a field, filter name, parameter name, or similar technical identifier, it does not need to be replaced.
13	docs\docs-ref-autogen\excel_1_20\excel\excel.interfaces.chartmapoptionsdata.yml	country	52	2	Replacement required	Geopolitical	Details The term `country` is used as a mapping level option in a region map chart, which is effectively labeling a country/region list or resource. To avoid geopolitical issues, it should be replaced with `country/region`.
14	docs\docs-ref-autogen\excel_1_20\excel\excel.chartmaparealevel.yml	country	37	2	Replacement required	Geopolitical	Details The term `country` is used as an enum member to label a mapping level in a chart, which is effectively labeling a country/region list or resource. To avoid geopolitical issues, it should be replaced with `country/region` for consistency and inclusivity.
15	docs\docs-ref-autogen\excel_1_20\excel\excel.chartmaparealevel.yml	country	38	2	Replacement required	Geopolitical	Details The term `country` is used as a label for a map area level in an enum that categorizes geographic regions, similar to city, continent, and state. In this context, it is labeling a country/region resource and should be updated to avoid geopolitical issues. It should be replaced with `country/region` for consistency and inclusivity.
16	docs\docs-ref-autogen\excel_1_20\excel\excel.chartmaparealevel.yml	country	43	2	Replacement required	Geopolitical	Details The term `country` is used as a value in an enum that labels mapping levels for chart areas, which is effectively labeling a country/region resource. To avoid geopolitical issues, it should be replaced with `country/region`.
17	docs\docs-ref-autogen\excel_1_20\excel\excel.chartmapoptions.yml	country	63	2	Replacement required	Geopolitical	Details The term `country` is used as a string literal value in an API property to specify a mapping level for a region map chart. This is effectively labeling a country/region list or resource, so to avoid geopolitical issues, it should be replaced with `country/region`.
18	docs\docs-ref-autogen\excel_1_20\excel\excel.chartmapoptions.yml	country	67	2	Replacement required	Geopolitical	Details The term `country` is used as a mapping level option in a region map chart, which is effectively labeling a country/region list or resource. To avoid geopolitical issues, it should be replaced with `country/region`.

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[learn-build-service-prod]

Learn Build status updates of commit 0cdea05:

✅ Validation status: passed

File	Status	Preview URL	Details
.gitignore	✅Succeeded
docs/docs-ref-autogen/common_preview/toc.yml	✅Succeeded	View (common-js-preview || outlook-js-preview || excel-js-preview || onenote-js-1.1 || powerpoint-js-preview || word-js-preview)
docs/docs-ref-autogen/common/toc.yml	✅Succeeded	View (>=common-js || >=outlook-js-1.1 || >=excel-js-1.1 || onenote-js-1.1 || >=powerpoint-js-1.1 || visio-js-1.1 || >=word-js-1.1) View (common-js || <outlook-js-preview || <excel-js-preview || <powerpoint-js-preview || <word-js-preview) View (common-js-preview || outlook-js-preview || excel-js-preview || onenote-js-1.1 || powerpoint-js-preview || word-js-preview)
docs/docs-ref-autogen/excel_1_1/toc.yml	✅Succeeded	View (excel-js-1.1)
docs/docs-ref-autogen/excel_1_10/toc.yml	✅Succeeded	View (excel-js-1.10)
docs/docs-ref-autogen/excel_1_11/toc.yml	✅Succeeded	View (excel-js-1.11)
docs/docs-ref-autogen/excel_1_12/toc.yml	✅Succeeded	View (excel-js-1.12)
docs/docs-ref-autogen/excel_1_13/toc.yml	✅Succeeded	View (excel-js-1.13)
docs/docs-ref-autogen/excel_1_14/toc.yml	✅Succeeded	View (excel-js-1.14)
docs/docs-ref-autogen/excel_1_15/toc.yml	✅Succeeded	View (excel-js-1.15)
docs/docs-ref-autogen/excel_1_16/excel/excel.cardlayout.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.cardlayoutsection.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.cellvalue.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.cellvalueandpropertymetadata.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.compactlayout.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.entitypropertytype.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.errorcellvalue.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/excel/excel.referencedvalue.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_16/toc.yml	✅Succeeded	View (excel-js-1.16)
docs/docs-ref-autogen/excel_1_17/excel/excel.cardlayout.yml	✅Succeeded	View (excel-js-1.17)
docs/docs-ref-autogen/excel_1_17/excel/excel.cardlayoutsection.yml	✅Succeeded	View (excel-js-1.17)
docs/docs-ref-autogen/excel_1_17/excel/excel.cellvalue.yml	✅Succeeded	View (excel-js-1.17)
docs/docs-ref-autogen/excel_1_17/excel/excel.cellvalueandpropertymetadata.yml	✅Succeeded	View (excel-js-1.17)
docs/docs-ref-autogen/excel_1_17/excel/excel.compactlayout.yml	✅Succeeded	View (excel-js-1.17)
docs/docs-ref-autogen/excel_1_17/excel/excel.entitypropertytype.yml	✅Succeeded	View (excel-js-1.17)

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.