Tag: Office 365

Azure VPN – Change Local Site Public IP

If a Clients Local site public IP changes the VPN tunel betwen Azure and the Local Site will disconnect. To fix this do the following:

Connect to Azure using powershell and run the following command:

New-AzureRmLocalNetworkGateway -Name LocalSite -ResourceGroupName [ClientRG] -Location ‘northeurope’ -GatewayIpAddress ‘[Public wan IP 2.4.6.8]’ -AddressPrefix ‘[LAN IP Net 192.168.1.0/24’

 

(Change the RG and Public wan IP and the LAN IP Net to the correct settings)

Office 365 Add calendar permissions with powershell

To add permissions on a Exchange Object in Office 365 using PowerShell the cmdlet set-MailboxFolderPermission or add-MailboxFolderPermission can be used.

In this example we add editor permissions for user2 to user1’s calendar. This will enable user2 to edit, add or delete content of user1’s calendar.

set-MailboxFolderPermission -Identity user1@domain.no:\calendar -user user2@domain.no -AccessRights Editor

Note: kalender is the Norwegian Word for Calendar

To bulk add all users in a Tennant as Reviewer to user1@domain.no’s calendar run the following cmdlet.

$Users = Get-Mailbox | Select-Object -ExpandProperty userprincipalname
ForEach ($user in $Users )
{
Add-MailboxFolderPermission -Identity “user1@domain.no:\calendar” -User $User -AccessRights Reviewer
}

For full details of this cmdlet:
https://technet.microsoft.com/en-us/library/dd298062(v=exchg.160).aspx

And for my original Source:

Add Calendar Permissions in Office 365 via PowerShell

Installing modules is easy – Azure and Office365

This little post is to get you up and running with Azure PowerShell so that you can manage your Azure subscriptions and Office365 tenants in 10 minutes after booting up an fresh install of Windows 10.

I have tested this in the following Windows builds:
10586 (1511 build – Windows 10)
10586(TP4 build – Windows Server 2016)
14328 (insider build – Windows 10)

Simply start PowerShell in Elevated mode (right click on PowerShell and start in Admin mode.

type these 3 lines – one at a time.

“Install-Module AzureRM -force:$true”
“Install-Module Azure -force:$true”
“Install-Module MSOnline -force:$true”

When the installation is finished you need to set the execution policy to “Unrestricted” to be able to connect to Office365 tenants.

“Set-ExecutionPolicy Unrestricted”

You are good to go! 🙂
Good luck playing around with Azure and Office365

 

 

Managing Office 365 and Exchange Online with Windows PowerShell

Connect to Office 365 PowerShell
Connect to Exchange Online PowerShell
Connect to Office 365 Compliance Center PowerShell
Connecting to Skype for Business Online by using Windows PowerShell
Set up the SharePoint Online Management Shell Windows PowerShell environment

Sorurce: https://support.office.com/en-gb/article/Managing-Office-365-and-Exchange-Online-with-Windows-PowerShell-06a743bb-ceb6-49a9-a61d-db4ffdf54fa6?ui=en-US&rs=en-GB&ad=GB

SMTP Relay in Office365

When sending email from i.e. Visma or other 3. party applications you need a SMTP server. Some times you can use the local ISP SMTP server, but then you need to add that SMTP server to yours domain SPF record. You might don`t wnat to do this.

 

Here is the solution:

Log in to the tennant, and start Exchange management console.

Create a connector filtering on the public IP address beeing used for the server that hosts Visma.

In Visma add a SMTP server using your MX record for that tennant (i.e. itstyring-no.mail.protection.outlook.com​ ) and port 25.

 

This connector will relay email with from addresses containing a valid domain for that tennant.

OneDrive for Business – ​The server you are trying to access is using an authentication protocol not supported by this version of Office.

OneDrive for Business – ​The server you are trying to access is using an authentication protocol not supported by this version of Office.

We ran into this error and found the following fix at community.office365.com

1.Accessed Control Panel > Selected the Microsoft Office Subscription > right clicked > change > Selected Online Repair
2.Removed all the stored credentials in the credentials manager (control panel > credentials manager)
3. Restarted the computer
4. Deleted the folder’s below:
C:\Users\username\AppData\Local\Microsoft\Office\Spw
C:\Users\username\AppData\Local\Microsoft\Office\16.0\OfficeFileCache
5. Sign in Word (opened blank document > file > account > signed out and signed in office 365 account)
6. Started OneDrive for Business. ( from the search bar typed OneDrive for Business> clicked on the app > sync a different library instead >pasted the url of the team site “Public documents” > sync now​

Source:
https://community.office365.com/en-us/f/154/t/410059

Allow external senders in Public folder – Office365

Public folders are set to NOT allow external senders to public folders in Office 365. This can be fixed using the following receipt:

Conncect to the Windows Azure Active Directory Module for Windows PowerShell using the following commands.
Create a placeholder for your credentials:
$LiveCred = Get-Credential

Popup box will ask for your Office 365 Global Administrator credentials.

Create a placeholder for your Powershell Session towards Exchange Online.
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection

Import your Powershell Session to connect to Exchange Online.
Import-PSSession $Session

Run this command to allow all scripts:
set-executionpolicy unrestricted

Then the public folder part
Add-PublicFolderClientPermission \(Path of the Public folder name) -User Anonymous -AccessRights CreateItems

Change Default emailadress on Public folder in Office365

The problem:
A public folder in Office 365 Hosted Exchange will be assigned a @onmicrosoft.com address by default. And there is of cource no way of changing this to your primary domain.

Solution:
Conncect to the Windows Azure Active Directory Module for Windows PowerShell using the following commands.
Create a placeholder for your credentials:
$LiveCred = Get-Credential

Popup box will ask for your Office 365 Global Administrator credentials.

Create a placeholder for your Powershell Session towards Exchange Online.
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection

Import your Powershell Session to connect to Exchange Online.
Import-PSSession $Session

Run this command to allow all scripts:
set-executionpolicy unrestricted

Then run the following command to disable the Policy for assigning email Adresses in public folders.
Set-MailPublicFolder -Identity “\” -EmailAddressPolicyEnabled $False

Now, in your Office 365 tennant web admin go to Exchange – Public Folders – Highlight the public folder (email enabled) – Click the pencil (edit) – Click on Email Address – highlight the address you want to use as default – Click pencil – Check the default email address checkbox.
Save, close and test.

SPF 1-2-3

Here is a quick intro to SPF and how to configure it:

SPF (Sender Policy Framework) is a countermeassure for beeing an unwilling wictim of spam sending. Using SPF you can approve from what SMTP servers email from @yourdomain.com will be sent from. This will make it harder to spoof your e-mail adrress, as long as the receipient server checks the SPF record.

For Office365 you need to update your DNS zone with SPF records to fully validate the domain. Here is an example of how the SPF record shuld look like:

v=spf1 include:spf.protection.outlook.com -all

If you are using some system to send out e-mails outside Office365 you need to add those servers to you SPF record.
If you just want to add a IP adresse this is how your record shuld look like:
v=spf1 include:spf.protection.outlook.com ip4:11.11.11.18 -all

And if you want to use a hostname (and a IP address) it could be like this:
v=spf1 include:spf.protection.outlook.com ip4:11.11.11.18 a:mail.sender.com -all

Note that using include will require the domain (ie_ spf.protection.outlook.com) to have its own SPF record to be valid.