I didn't understand this task, it was sent to email in doc format: 1. Need to design and write script that will resolve with 2 artifacts in same folder: package and the manifest file with the following restrictions a. The scripts get 3 params: Package, Action, Target Cloud b. Each Cloud has its own state of available Loaders: i. Cloud1 – GalleryAction only ii. Cloud2 – GalleryAction & CatalogAction iii. Cloud3 – CatalogAction only c. Manifest must include both Loader sections. If not needed, leave data empty as shown in the example below. d. Supported Actions: Upload, Delete, UploadCuration For Upload or UploadCuration actions the PackagePath value is mandatory. For Delete action it is redundant. e. For UploadCuration action ‘Location’ param is also mandatory. Manifest Path The manifest file name must be 'AzureServicesFlowManifest.json' The Path should be [20200419-114306]/AzureServicesFlowManifest.json Path is arbitrary after the root "/", everything arrives at the high side relative to the root path, so it deepens on the packer (low side component which generates the package) and the loaders at the high side to agree on the format of the paths We Settled down on this format: Path: Get-Date -Format "yyyyMMdd-HHmmss" e.g 20200419-114306

Network Isolation Overview Azure Services that exposes public internet facing endpoints should get compliant with DIAMOND M2 requirements to lock down the endpoint to authorized callers. There are different mechanisms to provide the required network isolation based on the service type. This document covers the different service types and corresponding actions to be taken by each type. You can also review Network Isolation M2 Scope for Network Isolation In scope: All Azure Services with one or more endpoints that are publicly exposed in the Internet (public IP address) are in scope for Network Isolation. Out of Scope: All Azure services with no Public Endpoints are out of scope. (3 sheets of description)

Questions about network security - firewalls.