Skip to main content

Hi all,

We’ve managed to import most of our subscriptions from our Azure tenant, but we’re struggling with the last three. They seem to fail without providing any meaningful error message. I’ve spoken to support, who suggest it may be due to 1) The number of resources or 2) The size of the subscriptions.

I understand that I need to split them up, which is going to be a hassle! However, I can’t be the only LucidScale user facing this issue. So, I’m reaching out to ask if anyone has any recommendations for splitting them up or tips on how you manage these in Lucid.

@Lucid: It would be really helpful if the error messages were more detailed, indicating exactly where the process failed so we could troubleshoot ourselves and know how best to split them if this is the only way to proceed. Also any white paper on the amount of resources etc. per sub we are limited to would also be advantageous

Thanks,
Nick J

@nickjames2006 Happy belated holidays! 

The article about importing Azure into LucidScale is here:

https://help.lucid.co/hc/en-us/articles/16080061445908-Import-and-manage-Azure-infrastructure-data-in-Lucidscale#imported-subscriptions

If the article doesn’t have what you’re looking for, at the end of the article it says “Give feedback on this article.” That’s where I would recommend reposting your last paragraph.

The easiest way to handle this situation is to delete unnecessary resources or subscriptions, but if they are all equally important, that might not be feasible.

If the article doesn’t help and deleting doesn’t help, and since you’ve already submitted a support ticket, the first thing I think when I read your post is that it would be better in the product feedback section. You can propose what you would like to see from LucidScale and other users can upvote your suggestion. If there are enough votes, your suggestion could be integrated into the newest release.


Reply