search

Azure / azure-resource-manager-schemas

Schemas used to author and validate Resource Manager Templates. These schemas power the intellisense and syntax completion in our ARM Tools VSCode extension, as well as the Export Template API
MIT License
611 stars 517 forks source link

Sendgrid Account resource type in ARM not available anymore? #1983

Closed santo2 closed 2 years ago

santo2 commented 2 years ago

Hi,

we a resource of type "sendgrid account" that we added to our ARM template. when we now look at the azure portal, we see that this sendgrid account has been mitigated

This SendGrid account resource has been migrated to a Software as a Service (SaaS) account.

We see that a resource of type SaaS is added for each sendgrid account. So what does that mean in terms of ARM? Is this completely removed now? Where can I now create and/or manage this SaaS resource? What should happen to the current sendgrid account resource?

anthony-c-martin commented 2 years ago

@santo2 does the information provided in this thread help?

https://docs.microsoft.com/en-us/answers/questions/559161/sendgrid-as-saas-resource-arm-template-deployment.html

santo2 commented 2 years ago

Hi, isn't there official documentation on how to create SAAS with ARM? because I can't seem to find it in the ARM template reference, and also not in the schemas in my visual studio code extension for azure bicep.

And should we keep the old resource "Sendgrid Account", or can it just be deleted?

anthony-c-martin commented 2 years ago

Hi, isn't there official documentation on how to create SAAS with ARM? because I can't seem to find it in the ARM template reference, and also not in the schemas in my visual studio code extension for azure bicep.

And should we keep the old resource "Sendgrid Account", or can it just be deleted?

@bmoore-msft, do you happen to know who could answer this question?

anthony-c-martin commented 2 years ago

@santo2 to work around the fact that you can't currently export this resource type, one option is to use Azure CLI to fetch the resource body in JSON format:

# replace <rgName> & <resName> with the resource group name and the name of the SaaS resource
az resource show -g <rgName> -n <resName> --resource-type "Microsoft.SaaS/resources" --api-version 2018-03-01-beta

You'd then be able to get a workable Bicep file (unfortunately without intellisense) by manually converting the JSON to Bicep and inserting the resource of format:

resource saasRes 'Microsoft.SaaS/resources@2018-03-01-beta' = {
  ...properties from Az CLI response...
}
santo2 commented 2 years ago

our previous sku is legacy-silver, but I guess that I need to choose a new value now. I'm not sure what the difference between legacy and current essentials or pro are. does anyone know a link which explains to me if I can go from legacy-silver to essentials40k without losing functionality?

bmoore-msft commented 2 years ago

I'm not sure what happened to the sendgrid RP but does appear to be gone ;) I would reach out to sendgrid support to see what the status is...

naeisner commented 2 years ago

  1. We see that a resource of type SaaS is added for each sendgrid account. Yes, this resources are the new accounts that was migrated from the old SendGrid account resources

  2. So what does that mean in terms of ARM? Is this completely removed now? What should happen to the current sendgrid account resource? The old SendGrid account resources was migrated but still exists on ARM. But its only used to link to the new account it does not have any account under it, and you won't be charged extra for it. It will be removed from ARM after a transition period (about ~2 months).

  3. Where can I now create and/or manage this SaaS resource? Under SaaS, you can see the resource, manage them, and create new ones

  4. Regarding deployment of SaaS sendgrid account via arm template a. Customers shouldn’t use the old arm template to deploy old Dev Services SendGrid resources, because this is deprecated b. It is technically possible to deploy the new SaaS SendGrid resources with ARM templates, however once deployed customers still need to manually activate the account from the portal before it can be used. Because of this manual activation, ARM template deployment is not officially supported.

  5. Regarding the pricing plan The legacy plan name will be preserved and you should see in your case "silver" indicated on the new migrated SaaS app.

Summary: We are planning to automatically remove the Dev Service resources in the next few months. Please leave them in your account during this transition period. For new applications, the link Anthony provided should be a good reference, however you will still need to activate any new SendGrid accounts in the portal under SaaS.

santo2 commented 2 years ago

Thanks for the feedback, I guess I'll just delete this in the ARM templates then.