AnsweredAssumed Answered

Office 365 provisioning using custom form

Question asked by Rajkiran Paul on Oct 13, 2016
Latest reply on Nov 7, 2016 by Rajkiran Paul

Like • Show 0 Likes0
Comment • 4

we have 3 capabilities in our office 365 connector.

1)create mail box

2)remove mail box

3)add license to user.

we are collecting Office 365 account via office 365 account collector.There licenses are coming as a attribute of the account.Suppose user have 2 license or 1 license .The license are coming in a format {organization:license1,organization:license2} or {organization:license1} or {organization:license2}.

In side our form it is displaying like {organization:license1,organization:license2} format. which is not correct.

so we are collecting license separately from some csv file as a account collector.

now how to provision user to office 365 using a form where i can select user & license and is there any change in the default afx fulfillment????

please show me the whole process?

No one else has this question

Outcomes

Akriti Chauhan

Oct 19, 2016 5:27 AM

Create mailbox command of Office365 connector can be used to provision user to Office365.

When we create an Office365 application, it automatically creates an account template and 'CreateAccount' form with it and does the appropriate mapping as well. So, Create Account for the application will create an Office365 account and mailbox.

But, this will not give any license to the created account on Office365. So, if you want to create a licensed account on Office365 using the AFX Connector, it is a two step process.

1. Create Mailbox (As explained above)

2. Add User License

So, first create the Office365 application. Use 'Create Account' which will create the specified account on Office365 and its mailbox. Run the Account collector and collect the created account. Use 'AddUserLicense' command of Office365 connector to give License to the created account.

Paramaters required to use 'AddUserLicense' are as follows:

1. AdminAccountName: Office365 administrator user name (A user that has admin rights to manage accounts, groups etc. on Office365 portal)

2. AdminPassword: Password for the Office365 administrator user above

3. UserPrincipalName: UserPrincipalname of the office365 user who should be granted the license (eg: xyz@organizationname.onmicrosoft.com)

4. Location: User location. Valid value for this is the 2-letter country code (eg: IN for India)

5. LicenseName: Name of the license to be granted.

Actions

Rajkiran Paul @ Akriti Chauhan on Nov 3, 2016 2:25 PM

Hi Akriti, thanks for the response.

1)How to collect those licenses from the office 365?As of now we are manually creating form field with available license type? Is it possible to collect license as entitlement from office 365?

2)our requirement is when the new user join we want to create office 365 account with license as a birth right provisioning?

we are able to add the license manually via access request form and afx fulfillment.We are trying to automate this task as birth right provisioning?

Actions

Akriti Chauhan

@ Rajkiran Paul on Nov 7, 2016 6:13 AM

Hi,

1) As per the current implementation, Office365 collector does not collect licenses as entitlements. We will have to check the feasibility of this implementation.

2) creating an account on Office365 and adding license to the user will not happen in one go. I think, you can achieve this by having two provisioning nodes (first for account creation and second for adding license to the created account) in your joiner workflow.

Actions

Rajkiran Paul @ Akriti Chauhan on Nov 7, 2016 6:22 AM

Hi Akriti ,Once again thank you.

could you please explain how to configure the joiner workflow for those 2 nodes i.e create mailbox and add licenses?

Actions

4 Replies

Akriti Chauhan Oct 19, 2016 5:27 AM
Mark Correct
Correct Answer
Create mailbox command of Office365 connector can be used to provision user to Office365.
When we create an Office365 application, it automatically creates an account template and 'CreateAccount' form with it and does the appropriate mapping as well. So, Create Account for the application will create an Office365 account and mailbox.
But, this will not give any license to the created account on Office365. So, if you want to create a licensed account on Office365 using the AFX Connector, it is a two step process.
1. Create Mailbox (As explained above)
2. Add User License

So, first create the Office365 application. Use 'Create Account' which will create the specified account on Office365 and its mailbox. Run the Account collector and collect the created account. Use 'AddUserLicense' command of Office365 connector to give License to the created account.

Paramaters required to use 'AddUserLicense' are as follows:
1. AdminAccountName: Office365 administrator user name (A user that has admin rights to manage accounts, groups etc. on Office365 portal)
2. AdminPassword: Password for the Office365 administrator user above
3. UserPrincipalName: UserPrincipalname of the office365 user who should be granted the license (eg: xyz@organizationname.onmicrosoft.com)
4. Location: User location. Valid value for this is the 2-letter country code (eg: IN for India)
5. LicenseName: Name of the license to be granted.
Like • Show 1 Like1
Actions
- Rajkiran Paul @ Akriti Chauhan on Nov 3, 2016 2:25 PM
  Mark Correct
  Correct Answer
  Hi Akriti, thanks for the response.
  
  1)How to collect those licenses from the office 365?As of now we are manually creating form field with available license type? Is it possible to collect license as entitlement from office 365?
  2)our requirement is when the new user join we want to create office 365 account with license as a birth right provisioning?
  
  we are able to add the license manually via access request form and afx fulfillment.We are trying to automate this task as birth right provisioning?
  Like • Show 0 Likes0
  Actions
  - Akriti Chauhan @ Rajkiran Paul on Nov 7, 2016 6:13 AM
    Mark Correct
    Correct Answer
    Hi,
    1) As per the current implementation, Office365 collector does not collect licenses as entitlements. We will have to check the feasibility of this implementation.
    2) creating an account on Office365 and adding license to the user will not happen in one go. I think, you can achieve this by having two provisioning nodes (first for account creation and second for adding license to the created account) in your joiner workflow.
    Like • Show 0 Likes0
    Actions
    - Rajkiran Paul @ Akriti Chauhan on Nov 7, 2016 6:22 AM
      Mark Correct
      Correct Answer
      Hi Akriti ,Once again thank you.
      
      could you please explain how to configure the joiner workflow for those 2 nodes i.e create mailbox and add licenses?
      Like • Show 0 Likes0
      Actions

Office 365 provisioning using custom form

Outcomes

Related Content

Recommended Content