Hello @FrankvH  I am wondering how did you notice this archive device start reporting again? I assume you are seeing the 'inventory date' got updated daily?  Pier to the online help -- https://docs.flexera.com/FlexNetManagerSuite2019R2/EN/WebHelp/index.html#topics/Dev-Archived_Inventory.html "Tip:  If an inventory device that is  Archived  is unexpectedly matched in incoming inventory — that is, the device somehow reappears — then its status is automatically switched from  Archived  back to  Active , and it disappears from this listing and is once again available in the  All Inventory  page. Most of the time, though, a device disappears from this listing because it has finally been deleted." Hence what you are seeing seem odd, I will suggest opening a support ticket to your local support team for further investigation. For something quick, and if you are an on premise customer , you could try update this ComplianceComputer status from archive to active via a sql statement and closely monitor afterwards. If you are an cloud solution FNMS user, the 'status' switch is supposed to be done by the system automatically. So please no hesitate and reaching out our support team if is necessary.   Cheers ... View more

Here is a 'user-friendly' URL 🙂   https://docs.flexera.com/FlexNetManagerSuite2019R2/EN/WebHelp/index.html#tasks/ManageO365Connection_OLH.html   Cheers   ... View more

Here is a 'user-friendly' URL 🙂   https://docs.flexera.com/FlexNetManagerSuite2019R2/EN/WebHelp/index.html#tasks/ManageO365Connection_OLH.html   Cheers   ... View more

Here is a 'user-friendly' URL 🙂   https://docs.flexera.com/FlexNetManagerSuite2019R2/EN/WebHelp/index.html#tasks/ManageO365Connection_OLH.html   Cheers   ... View more

Hi @aprabha  You can still use either of the method suggest in the following documentation  https://ChangeToYourServerName/Suite/Help/webhelp/index.html#tasks/ManageO365Connection_OLH.html  #1 option - Using FlexNet Manager Suite’s Multi-Tenant App to Connect to Microsoft 365  means using Application ID  (on Beacon UI -> Inventory Setting -> Powershell connection ) has a pre-written application ID for Flexera Beacon.  As our documentation state it's hard coded " Application (client) ID :   5bb1a5a2-0d97-4335-9448-119f7b27aff9 Or you can register your own app in #2 option so you will need to register own azure app ,then copy the application ID into beacon UI. which is @#2 option -  Registering an app using the Azure portal to connect to Microsoft 365 Cheers   ... View more

Hi @aprabha  I will suggest start with having a read our product online help which contains the necessary instruction how to configure o365 adapter   https://ChangeToYourServerName/Suite/Help/webhelp/index.html#tasks/M365_RegisteringAppAzure_OLH.html#task_azure_regapp_gkb_1021219 "Note please 'ChnageToYourServerName' in URL"     ... View more

Hi @aprabha  I will suggest start with having a read our product online help which contains the necessary instruction how to configure o365 adapter   https://ChangeToYourServerName/Suite/Help/webhelp/index.html#tasks/M365_RegisteringAppAzure_OLH.html#task_azure_regapp_gkb_1021219 "Note please 'ChnageToYourServerName' in URL"     ... View more

Thank you for the valid workaround @michael_hoogen The product team has identified a defect logged under FNMS-68929.  An KB article is also created for the affected user to apply the workaround.   https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/Accessing-FNMS-site-returns-500-internal-server-error-after/ta-p/155013   Cheers Kevin  ... View more