Skip to main content

Require spacelift_azure_integration Terraform resource to output Object_id

Feature RequestsSpacelift Provider

The spacelift_azure_integration Terraform resource outputs the application_id (Azure AD Application/Client ID) but not the object_id, as per the provider documentation: https://registry.terraform.io/providers/spacelift-io/spacelift/latest/docs/resources/azure_integration If i need the object_id for Azure IAM resources,i have to retrieve it by looking up the service principal via the AzureAD provider: https://registry.terraform.io/providers/hashicorp/azuread/latest/docs/data-sources/service_principal. The reason the object_id is important is cause as per azure for there IAM Terraform resource we need to pass the object _id not the app id. This would be better if we could get that directly as an output rather than having to run about lookup to get the object id or manage it manually as a variable.

Workaround
Problem
Status: ✅ Completed5 comments

Log in to comment and vote

Comments5

  • Marcin Białoń

    Team•

    Nov 21, 2025

    We released a fix in v1.39.0 of the provider.

  • Jade Gust

    •

    Oct 8, 2025

    This is still an issue and incorrect @Marcin Białoń @Marcin Wyszynski

  • Purple Coast

    •

    Oct 8, 2025

    In all the tests conducted with different integrations, we noticed that the object_id value returned by the spacelift_azure_integration resource does not match the object_id shown in the Azure portal for the service principal created by the integration. Moreover, the returned value does not correspond to any of the properties of the service principal.
    Could you please review it and ensure that the correct value is being returned? Thank you!

  • Marcin Białoń

    Team•

    Sep 10, 2025

    Released in v1.32.0.

  • Black Breeze

    •

    Aug 22, 2025

    Thanks for bringing this up. I’ve opened an internal ticket with one of engineering teams to look into it. To be honest with you I don’t know if we actually have knowledge of this field’s value but if we do, I see no harm in exporting it as a resource attribute. Let’s see what the devs come back with.

    As a side note, you can also request provider changes directly through its repo - it’s open source. We accept pull requests, too.