3 ms·
Yup! { "$schema": "https://schema.management.azure.com/schemas/2019-08-01/managementGroupDeploymentTemplate.json# https://schema.management.azure.com/schemas
by firesteelrain 3y ago
Yup!
{
"$schema": "https://schema.management.azure.com/schemas/2019-08-01/managementGroupDeploymentTemplate.json# https://schema.management.azure.com/schemas/2019-08-01/manag...",
"contentVersion": "1.0.0.0",
"parameters": {
"location": {
"type": "string",
"defaultValue": "East US",
"metadata": {
"description": "Location for the resources."
}
},
"tenantAPlanName": {
"type": "string",
"metadata": {
"description": "Name of Tenant A's plan."
}
},
"tenantBPlanName": {
"type": "string",
"metadata": {
"description": "Name of Tenant B's plan."
}
},
"sharedServicesPlanName": {
"type": "string",
"metadata": {
"description": "Name of the Shared Services plan."
}
}
// Add more parameters as per your requirements
},
"variables": {
// Add variables if needed
},
"resources": [
{
"apiVersion": "2021-04-01",
"type": "Microsoft.Resources/resourceGroups",
"name": "[concat('SharedServices-', uniqueString(resourceGroup().id))]",
"location": "[parameters('location')]",
"properties": {}
},
{
// Define resources for Tenant A's plan
},
{
// Define resources for Tenant B's plan
},
{
// Define resources for the Shared Services plan
}
],
"outputs": {
// Define outputs if needed
}
}
I can get it to fill in the rest. I just go give it my requirements
- dinvlad 3y agoNever seems to work for me, unfortunately. Also the context window is too short so it chokes on giving me large outputs. And if doing it piecemeal, it would (partially) forget what it gave me in previous prompts. I feel like maybe my expectations are too high, but then as mentioned earlier, it’s much more productive for me to go find relevant example(s) on GitHub that have already been tested by a human.