Guest Expiration Date for Users

[Kamz]

Hello all, hoping you can help, kind of stuck here. I've been trying to figure out a way to build a flow that gets a guest user's expiration date, however I cannot figure out where that date is stored. I've checked Azure, Security, Compliance, you name it. 

I also followed this microsoft doc: https://learn.microsoft.com/en-us/sharepoint/dev/solution-guidance/manage-user-sharing-expiration

And it seems to error out "The property 'Expiration' cannot be found on this object. Verify that the property exists and can be set."

Anyone know where I can find where expiration is stored? I'd like to then do a scheduled flow of expiring users and email a list to stakeholders.

Thanks in advance.

[Expiscornovus · Accepted solution]

Hi @Kamz,

I would suggest to true the siteusers method of the SharePoint Rest API.

Below is an example for that.

_api/web/siteusers?$filter=IsShareByEmailGuestUser eq true&$select=LoginName,Email,Expiration

[Kamz]

Awesome, that worked like a charm. Any idea where that expiration data is stored though? Just curious.

[Expiscornovus]

Hi @Kamz,

I think that would be SharePoint, based on the fact that the links are shared via the application. 

But you never know with Microsoft. I will share if I find some evidence proving otherwise 😁

[Kamz]

@Expiscornovus so true. One more question if I may. I got it working, parsed the JSON, and created an array variable with the User email and expiration. How do I get those values into an HTML table that will then be emailed?

It seems if I try to use the var it puts all the data into 1 column, and if I try to use the prase JSON, it does for each.

Here's an example:

JonDoe@contoso.com	1/11/23
JaneDoe@contoso.com	1/12/23
MaryJ@contoso.com	1/13/23

[Expiscornovus]

Hi @Kamz,

I was actually writing up a blog about those steps 😁

Here is a screenshot of that whole flow.

[Kamz]

@Expiscornovus That looks awesome, didn't even think to use select action. But I feel like I'm missing something here

[Expiscornovus]

Hi @Kamz,

I used expressions for the value fields in the Select.

item()?['LoginName']

item()?['Email']

item()?['Expiration']

[Kamz]

@Expiscornovus Ya, I attempted that, but got the following error

Unable to process template language expressions in action 'Select' inputs at line '0' and column '0': 'The template language expression 'outputs('Send_an_HTTP_request_to_SharePoint')?['body']['LoginName']['Email']['Expiration']' cannot be evaluated because property 'LoginName' doesn't exist, available properties are 'd'. Please see https://aka.ms/logicexpressions for usage details.'.

Also, noted in your image example, it seems you're using the integrated HTTP Request values.
I feel as though my HTTP Request is returning a block instead of an array "d"?

[Expiscornovus]

Hi @Kamz,

Sorry for the confusion. I mean in the Map field in the right column of each row.

[Expiscornovus]

Hi @Kamz,

Just noticed I added Nometadata Headers to the Send an HTTP request. That explains why I am not getting the ['d'] property 😂

[Kamz]

@Expiscornovus Thanks, but what's throwing me off is the SP icon you're getting which implies the value is derived from the preceding action. I am only getting body, not body.value and when I try to input it in using an expression it rejects it in the Select action.  

BadRequest. The 'from' property value in the 'select' action inputs is of type 'Object'. The value must be an array.

This is what I have so far

Thanks

[Expiscornovus]

Hi @Kamz,

I am using the value property from the body. I used this expression in the From field of the Select action:

outputs('Send_an_HTTP_request_to_SharePoint')?['body']['value']

[Kamz]

@Expiscornovus I understand that part, I tried that before as seen below

But that's when I got the invalid template error mentioned before

 Unable to process template language expressions in action 'Select' inputs at line '0' and column '0': 'The template language expression 'outputs('Send_an_HTTP_request_to_SharePoint')?['body']['value'] ' cannot be evaluated because property 'value' doesn't exist, available properties are 'd'.

Guess this is good practice for troubleshooting for your new blog post on this haha

[Expiscornovus]

Hi @Kamz,

I had another look at one of your screenshots. It looks like you made a typo in the Accept and Content-Type header values.

It should be:

application/json;odata=nometadata

You used:

applications/json;odata=nometadata

[Kamz]

@Expiscornovus I just realized that after I sent the last reply... If we ever meet, be sure to give me a smack 😂 

[Expiscornovus]

Hi @Kamz,

Lol, don't worry. I make typos on a daily basis 😂