microsoft / azure-secure-enclave-for-research Goto Github PK

The creation of a public storage account, Data Factory, and Logic App should be optional.

After the st prefix, add a moniker to indicate private or public.

Also consider applying a different tag.

As shown at https://github.com/Azure/azure-managedapp-samples/blob/14f4db985e1f7fa3c99ad6575e4077e886a669c8/Managed%20Application%20Sample%20Packages/201-managed-app-using-existing-vnet/createUiDefinition.json#L91

Official doc: https://docs.microsoft.com/en-us/azure/azure-resource-manager/managed-applications/microsoft-network-virtualnetworkcombo

Need to apply a limit to the user provided workload name.

Currently, the secured (private) storage account in the research enclave only has a private endpoint for the blob endpoint enabled. To enable accessing the storage account using tools that support the ADLS Gen 2 protocols, the dfs endpoint also needs a private endpoint.

This involves creating a new private endpoint and a new private DNS zone. Currently, these resources are created in the storage_account.bicep file, but if multiple resources of those types will be created, they should be abstracted in modules.

Error: The workflow connection parameter 'azuredatafactory' is not valid. The API connection 'azuredatafactory' is not configured to support managed identity.

Set enablerdsaadauth:i:1 in RDP properties of the host pool

This will make it easier to begin deploying research compute in the enclave.

Hii ,
we have deployed this setup by using this github link, the system is up/running if anyone has the post deployment steps on how to connect and access azure virtual desktop
Kindly please send the link

Currently, the IP address ranges of new VNets are hardcoded in the Bicep template. Those IP ranges are used to create a new workspace and new access (AVD) VNet if needed.

The IP address ranges should be specified by the user.

In case private endpoint policies were specified for a subnet, it isn't correctly applied.