AnsweredAssumed Answered

Adding a license to O365

Question asked by Shlomo Katz on Feb 24, 2017
Latest reply on Nov 17, 2017 by Razvan Dumitriu

Like • Show 0 Likes0
Comment • 7

Hello

We have a O365 instance (no email) and I am trying to enable the connector for Add License fulfillment.

I have followed the Connector guide and used various configurations to get it to work.

The Test Capabilities return success.

When I put in a request, AFX reports that it is complete but I get the following error:

AFX will not handle this item because the command 'AddEntToAccount(AddEntToAccount)' is not supported on endpoint 'O365'

What am I missing?

Do we need to have email accounts in O365 for this to work?

We have other products enabled.

We are using UPN for resolution.

Thank you

Boris Lekumovich

Nov 15, 2017 9:17 PM

Correct Answer

RSA Ideas for RSA Identity Governance & Lifecycle

See the reply in context

No one else had this question

Outcomes

7 Replies

Pavan Naik Mar 6, 2017 9:43 AM
Mark Correct
Correct Answer
Hello,
For Office 365 connector, we only support 3 capabilities. Add/Remove mailbox for new user and add user license. Which connector template you are using for provisioning? You should not get error related to AddEntToAccount as this command is not supported in Office 365 connector. Can you mention the exact steps you are trying to follow for add license fulfillment.
1 person found this helpful
Like • Show 0 Likes0
Actions
- Razvan Dumitriu @ Pavan Naik on Nov 15, 2017 1:48 AM
  Mark Correct
  Correct Answer
  Hello Pavan Naik, Everyone.
  
  You mentioned "we only support 3 capabilities. Add/Remove mailbox for new user and add user license".
  Can you tell why a Remove User License would not be present, as to undo the Add operations? Or what was the concept behind in order to be used when integrating with Office 365?
  
  Thank you for your time and assistance.
  
  Razvan
  Like • Show 0 Likes0
  Actions
  - Pavan Naik @ Razvan Dumitriu on Nov 15, 2017 2:25 AM
    Mark Correct
    Correct Answer
    The support for the 3 capabilities is based on the requirement at the time of integration. We did not had requirement for
    "Remove user license", that is the reason we do not support it.
    
    Thanks,
    -Pavan
    Like • Show 0 Likes0
    Actions
    - Razvan Dumitriu @ Pavan Naik on Nov 15, 2017 5:35 AM
      Mark Correct
      Correct Answer
      Thank you for the prompt reply Pavan Naik.
      So this connector was made on purpose for a specific client integration, based on that client's own requirements?
      
      I am trying to understand RSA's proposed solution for integrating with Office 365 and managing the life-cycle and accesses of users.
      Like • Show 0 Likes0
      Actions
      - Francesco Moreno @ Razvan Dumitriu on Nov 15, 2017 3:58 PM
        Mark Correct
        Correct Answer
        HI Razvan,
        
        The standard O365 connector has been made based on the requirements we gathered from customers. If you want to add functionality to the connector you have the option to use an Request for Enhancement. Please make use of that option, it is our main input for gathering customers requirements and it is a very useful tool to steering RSA towards needed functionality.
        
        When customers need more functionality than is offered in our standard O365 connector and can not wait for the enhancement to go through is creating an own connector for example based on powershell. Customers then also have the option to either share that template on the community for others to use, or send it together with your Enhancement request to our engineering department. If it passes our quality tests then we could add that functionality to the O365 connector and we would maintain it. Of course you do can also just wait until we add that functionality ourselves.
        Like • Show 1 Like1
        Actions
        Boris Lekumovich @ Francesco Moreno on Nov 15, 2017 9:17 PM
        Unmark Correct
        Correct Answer
        RSA Ideas for RSA Identity Governance & Lifecycle
        Like • Show 0 Likes0
        Actions
        Razvan Dumitriu @ Francesco Moreno on Nov 17, 2017 7:10 AM
        Mark Correct
        Correct Answer
        Hello Francesco,
        
        Nice to hear from you and thank you for taking time to answer.
        I understand the RFEs, sent lots of those but, as initially stated, I was just trying to understand the concept behind the current set of operations, maybe a technical answer such as: a revoke is not needed because it is redundant to other operations, or we do not generate those operations in CRs so nothing to map to, or it is not needed because bla bl bla , or remove is done better in another way (like when you request a new license to be added, remove previous ones afterwards) etc etc.
        Sorry if it was misunderstood. I will take it as it is
        
        Have a nice weekend everyone.
        Like • Show 0 Likes0
        Actions

Adding a license to O365

Outcomes

Related Content

Recommended Content