'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Why Azure AD Adds the Creator as Group Owner via ServiceNow
Question details
The user wants to know why creating an Azure AD security group through ServiceNow automatically assigns the creator as the group owner.
- Product
- Azure AD and ServiceNow
- Device & OS
- not provided
- Scenario
- Creating a security group in Azure Active Directory using the ServiceNow Integration Hub (IHUB) Azure AD spoke.
- Observed behavior
- The logged-in user who initiates the group creation in ServiceNow is automatically set as the owner of the newly created Azure AD group.
Ensure you have administrative access to your ServiceNow instance and relevant Azure AD portal permissions to view group properties and integration logs.
Review Default Azure AD Behavior and Integration Documentation
Understand Microsoft's default behavior for group creation and consult official documentation to determine if ownership settings can be modified.
By design, Azure Active Directory automatically assigns the account or service principal that creates a group as its owner. When using the ServiceNow IHUB Azure AD spoke, the integration authenticates using specific credentials, which Azure recognizes as the creator.
To address this, you must review the official documentation for both platforms to see if post-creation ownership modification is supported in your workflow.
Visit the official Microsoft Learn site and search for Azure Active Directory group management fundamentals to understand the default ownership assignment rules.
Log into the ServiceNow Support portal and locate KB0635951 or similar articles covering known behaviors and configurations for the IHUB Azure AD spoke.
If you require a custom API workaround, post your specific workflow scenario in the Microsoft Q&A community under the Azure Active Directory tag.
Document Your Azure Integrations with WPS Office
While WPS Office does not directly manage Azure AD or ServiceNow configurations, it is the perfect free alternative to Microsoft Office for documenting your IT processes. Enjoy a familiar interface and seamless migration for all your technical drafting needs.
Frequently Asked Questions
Can I prevent the creator from becoming the group owner in Azure AD?
By default, Azure AD automatically assigns the creator as the owner. To change this, you typically need to run a subsequent API call or script immediately after creation to remove or replace the owner.
Where can I find the ServiceNow KB article for Azure AD spoke issues?
You can access specific knowledge base articles by logging into the ServiceNow Support portal and searching for the IHUB Azure AD spoke documentation or specific KB ID numbers like KB0635951.
Is the Integration Hub (IHUB) Azure AD spoke a Microsoft product?
No, the IHUB Azure AD spoke is developed and maintained by ServiceNow to facilitate integration and automation with Microsoft's Azure Active Directory services.
