Skip to content

Sample script: get report for SharePoint add-ins and azure acs retirement #5774

@mkm17

Description

@mkm17

Create a sample script that provides a report detailing the retirement status of components within the current SharePoint Online tenant


Original issue

Usage

m365 spo report retirementstatus

Description

Retrieve a report detailing the retirement status of components within the current SharePoint Online tenant

Options

Option Description
-s, --sharePointAddInsOnly [sharePointAddInsOnly] To get information about SharePoint add-ins only
-e, --eventReceiversOnly [eventReceiversOnly] To get information about Event Receivers only
-a, --azureACSOnly [azureACSOnly] To get information about Azure Access Control Service only

Examples

Retrieve information regarding the retirement of Azure ACS, SharePoint add-ins, and Remote Event Receivers.

m365 spo report retirementstatus

Retrieve information specifically about the retirement status of Azure ACS only.

m365 spo report retirementstatus --azureACSOnly

Retrieve information specifically about the retirement status of SharePoint add-ins and Remote Event Receivers.

m365 spo report retirementstatus --sharePointAddInsOnly--eventReceiversOnly 

Default properties

  • Type: (Azure ACS, SharePoint Add-in, Remote Event Receiver)
  • Path: (Specify the location or details related to the feature)
  • Suggestion: (Provide basic information on recommended replacements, e.g., for RER -> Webhooks)
  • Retirement Date: (Include the date when the feature is scheduled for retirement)

Additional Info

Hi everyone,

I have a proposal that I believe could greatly benefit our tenant administration process. I'm thinking of creating a report that provides insights into the retirement status of various features, such as the SharePoint Online add-ins and more. This report aims to help administrators be better prepared for upcoming feature retirements, ensuring a smoother transition. Some details are available here.

While I'm not certain about the feasibility of gathering all the information needed, I'm eager to hear your thoughts and suggestions on this idea.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions