Option 2:
Use the built in and use a connector that is IP auth'd

284bc4ae-b73b-42cd-a6a4-0366ca32847e-image.png

21ee0999-596f-4931-bad8-517bb0dd8f3a-image.png

bcfcfc92-41a6-4349-ab24-fc0a73b578fa-image.png

So Free/Busy would work on a federated level and you can actually use the schedule assistant from another Office 365 account to see that however that is all you will get. That said the user will need to send an invite regardless. There is a Uservoice on this
https://office365.uservoice.com/forums/273493-office-365-admin/suggestions/36486493-allow-calendar-updates-for-external-users

There are other options like setting up a calendar in Sharepoint and external users can do that.
https://support.microsoft.com/en-us/office/create-a-team-site-in-sharepoint-ef10c1e7-15f3-42a3-98aa-b5972711777d?ui=en-us&rs=en-us&ad=us

You can also use this enterprise app in Office 365 as well
https://techcommunity.microsoft.com/t5/microsoft-bookings-blog/you-can-now-do-more-with-microsoft-bookings/ba-p/298461

@DustinB3403 said in Office 365 Suite - User Licensing T&C:

And what I specifically was hoping someone had a link for was to MS's license or T&C saying that "no you can't share an account for multiple people".

Obviously this doesn't exists since the way the software is procured is per user.

Right, they won't repeat it because they have it in writing already. But you can always show that it is 1) assigned to a named user 2) at the time of procurement you have to agree to a single human.

That's better than any T&C link.

@dbeato said in 550 5.0.350 Remote server returned an error:

@WLS-ITGuy said in 550 5.0.350 Remote server returned an error:

@dbeato said in 550 5.0.350 Remote server returned an error:

@WLS-ITGuy said in 550 5.0.350 Remote server returned an error:

571 Delivery not authorized, message refused

That messages means a lot of things but yeah Whitelist on their Spam Filter end, Adding your IP to your SPF record, check if there is anything on the body of the message triggering the block on their end (i.e. URL or site link).

It is Office 365 with Exchange - I have created all the records that Microsoft wanted me to.

So, just to be clear, this is 100% not on my end, correct?

It shouldn't be on your end, the message is coming from the recipient's end server.

Right, which means that they received it.

@gjacobse said in PowerShell: Public Folder Search / remove:

Is this what I am looking for?

Remove-PublicFolderClientPermission -Identity "\My Public Folder" -User Contoso\Chris

Looks correct to me.

If you want to track email activity, you can Enable Mailbox Auditing for Office 365.

I believe if PowerShell is your method, you will not be able to do what you are trying to achieve. The only way now is to use the one that has just been advised.

@jaredbusch said in PS: O365 cmdlet issue.:

@gjacobse said in PS: O365 cmdlet issue.:

For my record later:

/wtb codeblock around that... ```

I fixed it.

We're having issues getting to the status and service health pages. Other then that email is flowing.

@scottalanmiller said in O365: OWA Recover deleted Calendar:

Now that we can mark them, I'm going to slowly try to work through getting them all closed.

I was going to unmark as question - since it was so old. I don't know if you can do that, but on topics of a certain age, you may do this rather then bringing them forward.

Up to you of course.

I have a number of non profits on the free E1 plan. Everything is the same except the bill. 🙂

Inserted a new line of code at line 82 and 87 to read as follows:

icacls \\<server>\d$\Users\$un\* /grant $un:F /inheritance:e /T

This line grants the new employee full access to their network folder and subfolders and items.

@stacksofplates I am pretty happy with it over all.

That moment when you have spent 3 hours waiting (5 min here and there) and then realize you are in the WRONG DNS Management Page....

smh

@scottalanmiller said in SharePoint Wiki examples:

@thwr said in SharePoint Wiki examples:

@scottalanmiller said in SharePoint Wiki examples:

@thwr said in SharePoint Wiki examples:

@fuznutz04 said in SharePoint Wiki examples:

I like the ability of a OneNote document, hosted in SharePoint, but don't like the lack of organization of it. I like Wiki's for documentation, because you can browse the wiki, copy/paste to/from it without accidentally deleting content. Once multiple people have their hands on a shared OneNote, in my opinion, it just becomes to easy to accidentally delete something.

That's one of the reasons why I'm looking for a 100% client-side wiki that just uses HTML5/JS. Just place that into a SharePoint doclib/dropbox/whatever

Not a bad idea.

Plus we don't need any proprietary software like OneNote, just a modern browser. Don't get me wrong, OneNote is a great tool, but I would like to have a wiki for my core documentation / admin KB.

But no tool found thus far?

Still checking available projects.

@Dashrender said in O365 and encrypted mail to other email systems:

I don't look at it as bleakly as you do. You in no way told the receiver they couldn't receive it, you told them they have to use a different method to receive it. Is it a good experience - I'm not going to argue that point, frankly I don't care as long as it works.

But you did... you sent them an email and the email didn't include the payload, it told you to go look in another system for the payload that didn't arrive (the princess is in another castle.) Why did you need the email if email isn't delivering the message? It's obviously similar to failure... two systems are being used for a single thing. All they want is the payload, not a message telling them about a payload elsewhere.

While the addin is removed, the links continued to appear until the below was completed

execute the below command via your PowerShell to o365

Set-OwaMailboxPolicy 'OwaMailboxPolicy-Default' -ReportJunkEmailEnabled $false

@coliver said in New MailUsers from Account - Office 365:

Resurrecting an old thread.

We ran into this issue again after updating to the most recent version of Azure AD Sync. We needed to set the mailnickname attribute in AD for the mail users to be created again. This was in addition to having the targetAddress declared.

Thanks for following up 🙂