![]() ![]() Only after you have safely copied your new client secret, select API permissions in the navigation bar, and then click Add a permission > Microsoft graph > Application permissions. Also record the Expires date, so you know the period of validity of your client secret (best practice is to set a reminder in your preferred enterprise technology calendar system to update the client secret shortly before it expires, as described in ). Important:You must immediately use the copy icon on the right of your new client secret value to capture the client secret and save it to a secure location where you can refer to it later, as it will not be shown in the Azure Partner Center again. Your new secret appears temporarily in the list of Client secrets. Shortly before the client secret expires, you need to generate a new client secret and update your add-in. c.Īdd a Description, which acts as a friendly name for your client secret.Ĭhoose how long your client secret should remain valid (between 6 months and two years).Ĭhoose a period that best suits your business processes. In the Client secrets section of the page, click New client secret.Ī new Add a client secret panel appears. In the navigation bar, select Certificates & secrets. If you wish to use a client secret to authenticate normal operations of the Microsoft 365 connector, add a client secret for the FlexNet Beacon add-in: Ĭlick Add URI to expose a field where you may enter your preferred value, and then click the check mark at the end of that field.Īfter a period of time, the registration completes, and the FlexNet Beacon overview page is displayed. On the FlexNet Beacon page, click Authentication in the middle navigation bar and do the following.Ĭhoose the redirect you would like to use, such as. The Azure AD application is created, and its FlexNet Beacon overview page appears. In the Supported account types section, choose Accounts in this organizational directory only. In the Register an application page, do the following: The Register an application page appears. In the left navigation bar, click Azure Active Directory. With an Azure account with Global Administrator privileges, login to the Microsoft Azure portal. To register an app in the Azure portal to connect to Microsoft 365: 1. Using this process, it is possible to specify a client secret (under OAuth) to be used for regular operation of the connector, so that a separate user name and password are not required for operational use. This requires Global Administrator privileges for the initial registration. If you would like instructions using the legacy Microsoft Office 365 (deprecated) connector, see Creating Connections Using the Microsoft Office 365 (Deprecated) Connector.Īn alternate method to the instructions provided in Using IT Asset Management’s Multi-Tenant App to Connect to Microsoft 365 is to register an app in the Azure portal to connect to Microsoft 365 as shown in the steps in this section. This is the recommended connector to use to create a connection to Microsoft Office 365 on an inventory beacon. Important:The instructions in this section are for use with the Microsoft 365 connector. Registering an App Using the Azure Portal to Connect to Microsoft 365 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |