Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Sendgrid Account resource type in ARM not available anymore?
See original GitHub issueHi,
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?
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
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
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).
Where can I now create and/or manage this SaaS resource? Under SaaS, you can see the resource, manage them, and create new ones
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.
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.
Thanks for the feedback, I guess I’ll just delete this in the ARM templates then.