IBM Security Verify Governance Adapter v 10.0.19 for Microsoft Azure Active Directory is available. Compatibility, installation, and other getting-started issues are addressed.
Copyright International Business Machines Corporation 2022,
2025. All rights reserved.
US Government Users Restricted Rights -- Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.
Welcome to the IBM Security Verify Governance Adapter for Microsoft Azure AD.
The Microsoft Azure AD Adapter is designed to create and manage User Accounts on the Microsoft Azure AD domain. The adapter runs in "agentless" mode and communicates using the Graph API to the Microsoft Azure Domain being managed.
The IBM Security Verify Governance Adapters are powerful tools that require Administrator Level authority. Adapters operate much like a human system administrator, creating accounts, permissions and home directories. Operations requested from the IBM Security Verify Governance Identity Manager server and IBM Security Verify Governance server will fail if the Adapter is not given sufficient authority to perform the requested task.
Review and agree to the terms of the IBM Security Verify Governance Adapter License prior to using this product. The license can be viewed from the "license" folder included in the product package.
Adapter Version
|
Component |
Version |
|
Build Date |
2026 June 09 23.50.09 |
|
Adapter Version |
10.0.19 |
|
Component Versions |
Adapter build: 10.0.19.1 Profile: 10.0.19.1 Connector: 10.0.19.1 Dispatcher 7.1.39 or higher (packaged separately) |
|
Documentation |
The following guides will be made available in the IBM Knowledge Center - Microsoft Azure Active Directory Adapter Installation and Configuration Guide |
New Features
|
Internal # |
Enhancement # (RFE / IDEA) |
Description |
|
|
|
Items included in 10.0.19 current release |
|
|
||
|
|
|
Items included in 10.0.18 release |
|
SVGAD-6132 |
ADAPT-249 |
|
|
SVGAD-6132 |
ADAPT-236 |
|
|
|
|
Items included in 10.0.17 release |
|
|
|
|
|
|
Items included in 10.0.16 release |
|
|
|
||
|
|
Items included in 10.0.15 release |
|
|
SVGAD-4276 |
ADAPT-190 |
|
|
|
Items included in 10.0.14 release |
|
|
|
None |
|
|
|
|
Items included in 10.0.13 release |
|
SVGAD-2424 |
ADAPT-160 |
Add role-assignable groups property to AzureADAdapter Group.
See Installation Guide > reference > From Default Group Attributes table for more details.
For errors, refer troubleshooting > Error messages and problem solving. |
|
Items included in 10.0.12 release |
||
|
|
|
|
|
SVGAD-2030 |
ISIM-I-5036 |
Azure Adapter should support custom and inactive roles |
|
SVGAD-2089 |
|
Properties file update for additional Attributes. Additional Attributes of the Azure Adapter need to be listed with additionalAttributes key as mentioned below: additionalAttributes=createdDateTime,ageGroup,businessPhones,companyName,consentProvidedForMinor,creationType,employeeHireDate,employeeId,employeeType,legalAgeGroupClassification,lastPasswordChangeDateTime,onPremisesDistinguishedName,onPremisesDomainName,onPremisesImmutableId,onPremisesLastSyncDateTime,onPremisesSamAccountName,onPremisesSecurityIdentifier,onPremisesSyncEnabled,onPremisesUserPrincipalName,passwordPolicies,preferredDataLocation,proxyAddresses,securityIdentifier,signInSessionsValidFromDateTime,imAddresses,provisionedPlans,licenseAssignmentStates,assignedPlans,onPremisesProvisioningErrors,deletedDateTime,signInActivity,division,costCenter,refreshTokensValidFromDateTime,employeeLeaveDateTime,employeeOrgData,manager,manager_FULLSUPPORT
|
|
Items included in 10.0.11 release |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
Items included in 10.0.10 release |
||
|
SVGAD-174 |
|
|
|
SVGAD-187 |
Added Support for Additional On-Premises Group Attributes. |
|
|
Items included in 10.0.9 release |
||
|
|
|
Azure - Adapter refresh and Guest account support |
|
Items included in 10.0.8 release |
||
|
|
|
Support has been added for a number of additional attributes which can be included or excluded by updating a configuration file. For more information regarding the attributes that are now available to be included/excluded and the configuration file specification see Chapter 3 and Chapter 7 of the updates to the installation and configuration guide paragraph. |
|
|
Items included in 10.0.7 release |
|
|
|
None |
|
|
|
Items included in 10.0.6 release |
|
|
|
None |
|
|
|
Items included in 10.0.5 release
|
|
|
None |
||
|
|
Items included in 10.0.4 release
|
|
|
None |
||
|
|
Items included in 10.0.3 release
|
|
|
None |
||
|
|
Items included in 10.0.2 release
|
|
|
None |
||
|
|
Items included in 10.0.1 release
|
|
|
|
None |
|
|
|
Items included in 7.1.9 release
|
|
|
|
None |
|
|
|
Items included in 7.1.8 release |
|
|
|
None |
|
|
|
Items included in 7.1.7 release
|
|
|
|
None |
|
|
|
Items included in 7.1.6 release |
|
|
|
167913 |
Azure Roles and Azure Licenses appear as Service Groups.
|
|
|
Items included in 7.1.5 release |
|
|
|
154049 |
Roles are dynamically populated for the given tenant via tha API when creating or modifying a user.
|
|
|
Items included in 7.1.4 release |
|
|
|
Add
support for IGI 5.2.2
|
|
|
|
Items included in 7.0.3 release |
|
|
|
136762 |
Added Configurable parameter to specify the Recon Page Size in Service Form
|
|
|
Items included in 7.0.2 release |
|
|
|
131874 |
Upgraded to Graph API version 1.6, support to the latest version provided by Microsoft.
|
|
|
Items included in 7.0.1 release |
|
|
|
Initial Release.
|
Closed Issues
|
Internal# |
Known Issue# / Case# |
Description |
|
|
|
|
|
Bug 4698 / SVGAD-6235
|
TS021690391 KI: DT472498
|
IBM SVG deletes Azure AD groups after a modification ofgroup name on the target. |
|
|
|
|
|
Bug 4343 / SVGAD-2394
|
TS016213757 KI: DT459321
|
Adapter giving timeout after 2 hours in filter recon. |
|
|
|
|
|
Bug 4601 / SVGAD-5083
|
TS019729914 KI: DT455021
|
Not able to create federated domain user. |
|
Bug 4597 / SVGAD-5087 |
TS019714653 KI: DT449880 |
DumpEntry() prints entry objects in the info log |
|
|
|
|
|
Bug 4582 / SVGAD-4882 |
TS019759177 KI: DT447526 |
|
|
Bug 4592 / SVGAD-4948 |
TS019931926 KI: DT448044 |
|
|
|
|
|
|
Bug 4487 / SVGAD-3655 |
TS018389418 KI: DT435016 |
|
|
Bug 4462 / SVGAD-3424 |
TS017014396 KI: DT421317 |
|
|
Bug 4486 / SVGAD-3647 |
TS017958504 KI: DT434365 |
|
|
SVGAD-3959 |
|
Recon process change to retrieve associated groups of the members based on number of users and groups |
|
SVGAD-4312 |
|
The adapter supports each user to enroll in 999 group only and 999 roles only, not beyond that. |
|
|
|
|
|
Bug 4367 / SVGAD-2574 |
TS016479139 KI: DT391647 |
|
|
Bug 4331 / SVGAD-2353 |
TS015988419 KI: DT391630 |
|
|
|
|
|
|
Bug 4272 / SVGAD-1834 |
TS014949696 KI: DT269784 |
|
|
Bug 4322 / SVGAD-2269 |
TS015959071 KI: DT378946 |
|
|
Bug 4193 / SVGAD-1195 |
TS014047624 KI: DT246577 |
False positive response when remove entitlement |
|
Bug 4273 / SVGAD-1830 |
TS015220425 KI: DT381609 |
Full Recon some groups are not being synced with associated members |
|
|
|
|
|
Bug 4291 / SVGAD-1980 |
TS014785408 APAR: DT257601 |
Azure Adapter is running very slow Performance enhancement of Full Recon. This is a fix which provide support of endsWithFilter on eruid (User Principal Name) only, which is also a part of performance enhancement. Microsoft document for filter - https://learn.microsoft.com/en-us/graph/filter-query-parameter?tabs=http. EndsWithFilter reconciliation support filtered user data. (* must be at first place only like given example) EndsWithFilter Example : (eruid=*@ibm.com) or (eruid=*abc@ibm.com) or (eruid=*@consultant.ibm.com) For below cases endsWithFilter with eruid will not work on API : 1. more than one * in the filter 2. * is not appears at first place like (eruid=abc*@ibm.com) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TS011850962 |
|
|
|
TS013089169 |
|
|
SVGAD-345 |
|
|
|
|
|
|
|
SVGAD-214 |
TS012598809 |
User Type Attribute support has been provided |
|
SVGAD-202 |
|
AzureAD password change request is not a password change request |
|
SVGAD-255 |
APAR IJ46544 |
|
|
SVGAD-204 |
|
|
|
Bug 3932 SVGAD-189 |
TS010289610 |
|
|
|
|
|
|
Bug 4036 |
TS012022819 |
ISVG - Azure connector moving to Stop with no reason |
|
Bug 3999 |
TS011223164 |
SVG 10 AZURE connector takes long time to Sync |
|
|
Items closed in 10.0.7 release
|
|
|
Bug 4058 |
TS012182768 |
Azure group members are missing in ISIM for few Azure AD groups. |
|
Bug 4048 RTC-191370 SVGAD-94 |
TS011983218 |
Adapter Azure AD - Problem Reconciliation |
|
Bug 3877 RTC-190922
|
TS009601235 |
Azure Adapter not retrieving more than 100 role or group memberships |
|
Bug 3798
|
TS008822467 |
Azure adapter |
|
Bug 4001 RTC-191165
|
IJ44919 TS011274307 |
SVG10 Azure 10.0.4 does not syncing one entry |
|
Bug 3849 RTC-190671
|
TS009152967 |
Azure recon filter fails |
|
|
Items closed in 10.0.6 release
|
|
|
RTC 191023 |
TS010589688 |
ISVG Microsoft cloud based adapters documentation clarification |
|
RTC 190548 |
ISIM 6.0 Microsoft Azure AD Adapter 6.0.9 - Customer questions |
|
|
|
Items closed in 10.0.5 release
|
|
|
RTC 190671 Bug 3849 |
TS009152967 |
Azure recon filter fail |
|
RTC 190673 Bug 3881 |
TS009629523 |
Reconcile Azure groups does not work correctly |
|
|
Items closed in 10.0.4 release
|
|
|
RTC 190567 Bug 3791 |
TS008284489 |
DN value too large when synching reconciled Azure AD groups to database |
|
RTC 190589 Bug 3828 |
TS009154416 |
Azure User and Group connector: connector config parameter "Application Key" is wrongly referenced |
|
RTC 190585 Bug 3830 |
TS009154081 |
Azure adapter full reconciliation does not return all account attributes |
|
|
Items closed in 10.0.3 release
|
|
|
Bug 3742 |
TS008090689 |
Strange behavior while reconciling accounts |
|
Bug 3748 |
TS008239362 |
Azure AD adapter update on user mail attribute |
|
Bug 3747 |
TS008340486 |
Azure AD Adapter Chinese Language Code is incorrect |
|
|
Items closed in 10.0.2 release
|
|
|
RTC-189750 Bug 3556 |
APAR IJ34789 TS005863375 |
Azure Adapter - Issues with the Azure AD Connector in ISIM |
|
|
Items closed in 10.0.1 release
|
|
|
RTC-187877 Bug 3343 |
APAR IJ28198 TS004183133 |
Azure Adapter - Token is not auto-regenerated on expiration |
|
|
Items closed in 7.1.9 release
|
|
|
RTC 186401 Bug 3159 |
APAR IJ22880 TS003347193 |
Azure adapter - Multivalued support for Administrator Role Membership attribute - erazureroleoid |
|
|
Items closed in 7.1.8 release
|
|
|
Bug 3063 |
|
Azure AD Adapter error during Change Log Sync operation |
|
Bug 3088 |
|
Adazure recon filter causes odata.error":{"code":"Request_BadRequest"} |
|
|
Items closed in 7.1.7 release
|
|
|
RTC 181613
|
Facing issue while performing Change Password operation for Azure adapter on IGI 5.2.5. |
|
|
Internal-RTC 181729
|
Internal D - As an Azure Developer, I must ensure that the adapter should create User in Active state when request is from IGI |
|
|
RTC 179378
|
APAR IJ09099, Bugz 2710 |
D - As an Azure adapter developer, I must ensure that the adapter sends back correct error message when user does not exist during a delete operation |
|
Internal- RTC 181519
|
Azure adapter Profile change for IGI 5.2.5 - eruid target attribute should be mapped to CODE governance attribute by default
|
|
|
|
Items closed in 7.1.5 release
|
|
|
154049 |
The 'directoryRoles' segment is used to manage roles instead of 'roles' and objectId to reference roles. This is due to a change in Microsoft API.
|
|
|
154150 |
52088,800,624/RTC 47191 |
The license removal needs an explicit call to remove the SKU in case no service plans are enabled. This is due to a change in Microsoft API.
|
|
|
Items closed in 7.1.4 release
|
|
|
|
Initial Release compliant with IGI 5.2.2
|
|
|
|
Items closed in 7.0.3 release
|
|
|
135407 |
App Key masked in the debug logs
|
|
|
136311 |
License deprovisioning fixed. Only the licenses which are enabled and applicable to User are allowed.
|
|
|
139239 |
ObjectId changed to roleTemplateId due to change in Microsoft API response
|
|
|
|
Items closed in 7.0.2 release
|
|
|
132799 |
The App key is hidden in service form. The attribute "erazureappkey" is added in password.attributes list in enRole.properties in <ISIM_HOME>/data directory.
|
|
|
|
Items closed in 7.0.1 release
|
|
|
|
Initial Release.
|
Known Limitations
|
Internal# |
APAR# / PMR# |
Description |
|
N/A |
N/A |
Attributes that require an SharePoint Online (SPO) license are not supported in the release of the adapter.
|
|
N/A |
N/A |
Attributes and/or operations that are not supported in the production version of Microsoft Graph API are not supported in the adapter.
|
|
N/A |
N/A |
Currently, we don't support
"Directory (Azure AD) extensions" attributes called also as the
custom attributes indicated in this document: |
|
N/A
|
N/A
|
The adapter doesn't support deletion of all mails in otherMails attribute in case of ISVG.
|
|
N/A |
N/A |
The adapter does not support case insensitive filter search with (eruid=username@domainname.com). This is a known issue with the Dispatcher which does filtering during reconciliation. Exact user name will need to be used during filter recon until this issue is fixed in the Dispatcher.
|
|
N/A |
N/A |
The adapter does not support duplicated Group Display Name.
|
|
N/A |
N/A |
The adapter does not support change of Group Name. This is a limitation of the IBM Security Verify Identity. Attempting to change the Group Name will result in the following error: " CTGIMI046E You cannot change the value of the attribute that is mapped to ergroupname."
|
|
N/A |
N/A |
The adapter does not support setting the group attribute 'mailNickName'. This is a limitation of the Windows Azure Active Directory Graph API. The API only accepts 'BposMailNickName' as the value for this attribute during group creation. Any other value will result in the following error: "Invalid value specified for property 'mailNickname' of resource 'Group'".
|
|
N/A |
N/A |
The service principal that represents the adapter service must be in an administrator role that has permissions to modify role objects to send POST or DELETE requests. It must be in a role that has permissions to read role objects to send GET requests. For more information about administrator roles in Windows Azure AD Graph, see Windows Azure AD Graph and Role-Based Access Control. http://msdn.microsoft.com/en-us/library/azure/dn385717.aspx
|
|
N/A |
N/A |
Microsoft has a limitation that user accounts cannot be added or modified in a federated domain from an on-premise Dir Sync Active Directory, which is not the default domain. Provisioning of users in such domain can be done by using the AD adapter and then syncing it back to the Azure Directory using the Microsoft DirSync tool.
|
|
N/A |
N/A |
The "Enable detailed TDI debugging" on the Service Form has been removed from 7.0.2 release due to security reasons. Instead, "DEBUG" in the ITDI log4j.properties file is to be used to enable extra debug logging.
|
|
N/A |
N/A |
Only the license and service plans that are enabled for provisioning and are applicable at the user level, are available for provisioning using the adapter. Company wide licenses are not supported.
|
|
N/A |
N/A |
User Principal Name is ReadWrite Attribute. It is not recommended to update User Principal Name from target as after reconciliation new user will be created and you need to associate user manually again for that user. Always prefer to update User Principal Name from ISIM/IGI to maintain consistency.
|
See the IBM Security Verify Governance Adapter Installation and Configuration Guide for detailed instructions.
Supported API
Now supporting Graph API.
Corrections to Installation Guide:
Chapter 1: Overview
Nothing to update
Chapter
2: Planning
Nothing to update
Chapter 3: Installing
Importing the adapter profile
For IGI only
Scenario A: Fresh Installation
If you are performing a completely new installation of the Azure Adapter, deploy AzureProfileGUID.jar directly. No further migration steps are required.
Scenario B: Upgrading Profile (AzureProfile.jar to AzureProfileGUID.jar)
If you are migrating an existing setup from AzureProfile.jar to AzureProfileGUID.jar resolving Known Issue DT472498 you must manually clear the connector cache to prevent synchronization conflicts.
Step 1: Import the Profile
1. Upload and import the new AzureProfileGUID.jar file into the IGI platform.
Step 2: Reset the Connector Cache
1. Log in to the IGI Administration Console.
2. Navigate to Enterprise Connectors > Monitor > Change Log Sync Status.
3. Locate your target Azure connector in the Connectors pane.
4. (Optional) Filter results by toggling the filter icon on/off, entering search criteria, and clicking Search.
5. Select the target connector, then click Actions > Reset.
6. Acknowledge any system alerts. When prompted with "Do you want to clear the connector cache?", click Yes.
7. Track the reset progress by opening the Sync History tab to verify that the synchronization starts cleanly with the new schema.
Chapter
4: Configuring
Nothing to update
Chapter
5: Troubleshooting
Error messages and problem solving
Add below error in Table1
|
Problem |
Corrective Action |
|
Reconciliation takes more than 24 hours. Or Reconciliation failed after 24 hours. |
Use Users Endpoint Filter Query at service level to filter out users and create more than one services of Adapter to fetch full set of data. |
Chapter 6:
Uninstalling
Nothing to
update
Chapter 7: Reference
Nothing to update
The IBM Security Verify Governance Adapters can be customized and/or extended. The type and method of this customization may vary from adapter to adapter.
Refer to the 'IBM Security Verify Governance Adapter Development and Customization Guide'
Support for Customized Adapters
The
integration to the IBM Security Verify Governance server "the adapter
framework" is supported. However, IBM does not support the customizations,
scripts, or other modifications. If you experience a problem with a customized
adapter, IBM Support may require the problem to be demonstrated on the GA
version of the adapter before a case is opened. q
Installation Platform
The IBM Security Verify Governance Adapter for Microsoft Azure AD was built and tested on the following product versions.
Adapter Installation Platform:
Due to continuous Java security updates that may be applied to
your IBM Security Verify Governance server and IBM Security Verify Governance
Identity Manager server, the following SDI releases are the officially
supported versions:
- Security
Directory Integrator 7.2 + FP14
- IBM
Verify Directory Integrator 11.0.0
- Security
Verify Directory Integrator 10.0.0 + LA0002** The
Dispatcher version 10.0.2 doesn't support installation using LA0002, please
install the Dispatcher10 prior to installing LA0002.
Note: Earlier versions of SDI that are still supported may function properly, however to resolve any communication errors, you must upgrade your SDI releases to the officially supported versions by the adapters. Please refer to the adapter's installation and configuration guides for the latest update on IBM Security Directory Integrator versions and fix packs
Managed Resource:
Azure AD supported HTTP Client component:
- Apache HTTP Component Client
3rd Party Client Libraries:
httpclient-4.5.14.jar
Download the httpclient-4.5.14.jar from
https://mvnrepository.com/artifact/org.apache.httpcomponents/httpclient/4.5.14
httpcore-4.4.16.jar
Download the httpcore-4.4.16.jar from
https://mvnrepository.com/artifact/org.apache.httpcomponents/httpcore/4.4.16
commons-logging-1.2.jar
Download the commons-logging-1.2.jar from
https://mvnrepository.com/artifact/commons-logging/commons-logging/1.2
Supported IBM Security Verify Governance servers:
- IBM Security Verify Governance Identity Manager v10.0*
- IBM Security Verify Governance v10.0
* Unless this document specifies a specific fix pack version of ISVG Identity Manager v10, we expect the adapter to work with ISIM 6 as well. However, it will only be debugged and fixed from the perspective of ISVG-IM v10.
This information was developed for products and services offered
in the U.S.A. IBM may not offer the products, services, or features discussed
in this document in other countries. Consult your local IBM representative for
information on the products and services currently available in your area. Any
reference to an IBM product, program, or service is not intended to state or
imply that only that IBM product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe any
IBM intellectual property right may be used instead. However, it is the user's
responsibility to evaluate and verify the operation of any non-IBM product,
program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to:
IBM
Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual
Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan
This information could include
technical inaccuracies or typographical errors. Changes are periodically made
to the information herein; these changes will be incorporated in new editions
of the publication. IBM may make improvements and/or changes in the product(s)
and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this
IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged should contact:
IBM
Corporation
2ZA4/101
11400 Burnet Road
Austin, TX 78758 U.S.A.
Such information may be available, subject to appropriate
terms and conditions, including in some cases, payment of a fee.
The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments
may vary significantly. Some measurements may have been made on
development-level systems and there is no guarantee that these measurements
will be the same on generally available systems. Furthermore, some measurements
may have been estimated through extrapolation. Actual results may vary. Users
of this document should verify the applicable data for their specific
environment.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available
sources. IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions
worldwide. Other product and service names might be trademarks of IBM or other
companies. A current list of IBM trademarks is available on the Web at
"Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Microsoft, Windows, and the Windows logo are trademarks of Microsoft
Corporation in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Oracle and/or its affiliates.