Skip to content

Latest commit

 

History

History
57 lines (41 loc) · 2.23 KB

readme.md

File metadata and controls

57 lines (41 loc) · 2.23 KB

JSON Sources

Validate Portal JSONs

We are currently making our web-pages from JSON files, our current JSON Portal sources are below.

Website Page to JSON Mapping

Website Page JSON Source
Home page / Admin Links Home page / Admin JSON
3rd Party Links 3rd Party JSON
US Government Links US Government JSON
End User Links/Apps End User JSON

Fields

Field Required
portalName Yes
primaryURL Yes
secondaryURLs No
note No

Secondary URLs

Secondary URLs is an array of icon/emoji/text and URL pairs. Each separate icon/text will be created as a link with the URL.

Notes

On some of the portals, we have been adding notes. For example:

Example: Using the notes to make old product name searchable for Defender products. Defender for Endpoint is shown with "previously Defender ATP"

Example: The new versus old Exchange Portals shown below.
Website has two Exchange Admin Centers with the New and Old portals noted

Example Portal Configuration

    {
    "portalName": "Microsoft Defender for Endpoints",
    "primaryURL": "https://securitycenter.windows.com",
    "secondaryURLs": [
          {
          "icon": "aka.ms",
          "url": "https://aka.ms/MDATPportal"
          }
        ],
    "note": "Previously Defender ATP"
    },

Additional context

Suggestions or context for the portals? If you are not certain about how to configure this, you may wish to create a New Issue instead.