Home > Uncategorized > 12 Comments on How To Change Your Office 365 App Password

12 Comments on How To Change Your Office 365 App Password

AzureAD conditional access EM+S enterprise mobility + security Exchange Online Protection IAmMEC Outlook OWA and Conditional Access: Inconsistent Error Reports.
May 24, 2017.
1 Comment on OWA and Conditional Access: Inconsistent Error Reports.
Here is a good error message.
Its good, because I could not find any references to it on Google and the fault was nothing to do with the error message: The error says “something went wrong” and “Ref A: a long string of Hex Ref B: AMSEDGE0319 Ref C: Date Time”.
The server name in Ref B will change as well.
It also says “more details” and if you click that there are no more details, but that text changes to “fewer details”.
As far as I have seen, this only appears on Outlook Web Access (OWA).
The error appears under these conditions: You are enabled for Enterprise Mobility + Security licences in Azure AD.
Conditional Access rules are enabled.
The device you are on, or the location you are at etc (see the specifics of the conditional access rule) mean that you are outside the conditions allowed to access Outlook Web Access.
You browsed directly to https://outlook.office.com or https://outlook.office365.com.
What you see in the error message is OWA’s way of telling you that you cannot get to that site from where you are.
That you have failed the conditional access tests.
On the other hand, if you visit the Office 365 portal or MyApps (https://portal.office.com or https://myapps.microsoft.com) and click the Mail icon in your Office 365 menu or on the portal homepage then you get a page that says (in the language of your browser): or in Welsh, This says “you can’t get there from here” and the reasons why you have failed conditional access.
If you were on a device or location that allowed you to connect (such as a device managed by Intune and compliant with Intune rules) then going to OWA directly will work, as will going via the menu.
So how can you avoid this odd error message for your users.
For this, you need to replace outlook.office.com with your own custom URL.
For OWA you can create a DNS CNAME in your domain for (lets say) webmail that points to outlook.office365.com (for this it will not work if you point the CNAME to outlook.office.com).
Your users can now go to webmail.yourdomain.com.
This will redirect the user via Azure AD for login and token generation, and as you are redirected via Azure AD you will always see the proper, language relevant, conditional access page.
Clutter Focused Inbox IAmMEC Outlook Bypassing Focused Inbox and Clutter Folders.
March 20, 2017.
No Comments on Bypassing Focused Inbox and Clutter Folders.
For the last few years Exchange Online mailboxes have been processed by a service call Clutter, which moved the less important emails, or indeed the clutter, to a dedicated folder.
This is now in the processes of being replaced by the Focused Inbox, which is client version dependant and is all based on views on the mailbox and not different folders.
The way to ensure mail is not marked as clutter, or shown in the Other view when your mailbox is processed by the Focused Inbox, is to mark the item as such, or to actively engage with the item.
That is if you reply or read the emails from these recipients they do not go into Clutter/Other, but if you ignore them or delete them before they are read then this makes them candidates for future processing by the Focused Inbox or Clutter engine.
There are though times when occasional emails need to be in your Inbox and not the Other view or the Clutter folder.
The best two ways to do this are as follows: Management Hierarchy.
The processing engine for Clutter/Focused Inbox will not place items from your Direct Reports or management chain in the Other view/Clutter folder nor will it place any emails from yourself into the low priority location.
The Direct Reports and your management chain is known to the processing engine as it is part of Active Directory.
So as long as your manager (and everyone else’s manager) attribute is populated in Active Directory and synced to Azure Active Directory then this configuration can be honoured.
Transport Rules.
The other way to ensure certain messages always go to the Inbox is to have the message processed by a transport rule.
Transport rules, like the management chain above are only available in Office 365 Business and not Outlook.com.
The two Transport Rule placeholders below add the Clutter and Focused Inbox rules (there are two different rules, so if you added the Clutter one in the past a new one is needed for Focused Inbox).
They add the rule with a arbitary placeholder, so that the rule never fires (unless you really happen to enter the demo text!).
So once you add these rules change them to suit the conditions of your environment.
For example if you have a “company wide communications” email sender then you could set the rule to be when that sender sends emails.
The two rule placeholders you need in remote PowerShell to Exchange Online are: 1: New-TransportRule -Name “Bypass Focused Inbox” -SubjectContainsWords “This is a placeholder rule that does nothing, change this action to suit the requirements of the client” -SetHeaderName “X-MS-Exchange-Organization-BypassFocusedInbox” -SetHeaderValue “true” -Comments “ – Any mail that meets the conditions of this rule will go into the Inbox or Focused Inbox and not the Clutter or Other folder in Exchange Online” 2: New-TransportRule -Name “Bypass Clutter” -SubjectContainsWords “This is a placeholder rule that does nothing, change this action to suit the requirements of the client” -SetHeaderName “X-MS-Exchange-Organization-BypassClutter” -SetHeaderValue “true” -Comments “ – Any mail that meets the conditions of this rule will go into the Inbox or Focused Inbox and not the Other view in Exchange Online” Change these rules to suit your requirements 2007 2013 2016 Edge EOP Exchange Online Protection FOPE IAmMEC Exchange Edge Server and Common Attachment Blocking In Exchange Online Protection.
March 6, 2017.
No Comments on Exchange Edge Server and Common Attachment Blocking In Exchange Online Protection.
Both Exchange Server Edge role and Exchange Online Protection have an attachment filtering policy.
The default in Edge Server is quite long, and the default in EOP is quite short.
There is also a few values that are common to both.
So, how do you merge the lists so that your Edge Server attachment filtering policy is copied to Exchange Online in advance of changing your MX record to EOP.
You run Set -MalwareFilterPolicy Default -FileTypes ade,adp,cpl,app,bas,asx,bat,chm,cmd,com,crt,csh,exe,fxp,hlp,hta,inf,ins,isp,js,jse,ksh,lnk,mda,mdb,mde,mdt,mdw,mdz,msc,msi,msp,mst,ops,pcd,pif,prf,prg,ps1,ps11,ps11xml,ps1xml,ps2,ps2xml,psc1,psc2,reg,scf,scr,sct,shb,shs,url,vb,vbe,vbs,wsc,wsf,wsh,xnk,ace,ani,docm,jar This takes both the Edge Server default list and the EOP default list, minus the duplicate values and adds them to EOP.
If you have a different custom list then use the following PowerShell to get your two lists and then use the above (with “Default” being the name of the policy) PowerShell to update the list in the cloud Edge Server: Get-AttachmentFilterEntry EOP: $variable = Get-MalwareFilterPolicy Default$variable.
FileTypes aadrm AIP Azure Information Protection encryption IAmMEC rms Azure Information Protection General Troubleshooting.
November 9, 2016.

Learn More Insights & Events
Monday September 07, 2020

C-Suite. C-Suite. C-Suite. An intelligent approach to informed patient care. Intelligent care leverages data and insights that are changing the face of care delivery as providers transition to new care models that are more predictive and personalized. This, along with the advancements in AI-based analytics …

The post Learn More Insights & Events appeared first on betfair.

3 Comments on Azure Information Protection General Troubleshooting

Azure Information Protection (AIP) is the new name, and new features for Azure Rights Management.
Azure Information Protection allows a company to create a series of labels to apply to documents and to have those documents tags and labelled.
For example a watermark or header is easy to set in the Azure Information Protection management blade in portal.azure.com.
In fact its so easy to turn on I did just that.
The actual work and business consulting with Azure Information Protection is the why and business reasons for using it rather than the technical steps to enable it.
So once I enabled it and the client installed I found that I had a banner toolbar in Office applications as shown: Clicking any of the labels will perform the default function of the product.
These can be modified in the Azure Portal as shown: The above two graphics show one example label (Confidential) that has had a sub label added (called NBConsult UK).
The larger image above shows the details for this “NBConsult UK” label.
In the properties blade for the label you can see I have turned on a template from RMS.
Once the changes are made and saved, you can publish the changes.
Clients will pick up these changes on restarting the client application.
And then started my issues and the steps to troubleshoot this.
First I got the following prompt twice: Followed by: And so I was finding my documents did not get the RMS based labels applied.
Reasons why this might be the case can be checked using the RMS tool in the Office application.
So I tried to protect the document manually via File > Info tab: This worked – I had the rights to use the template in the application – just AIP could not apply the template via the AIP tool.
To fix this I ran the Azure Information Protection (AIP) diagnostics tool.
To get this click the AIP lock icon and choose Help and Feedback from the menu: From this a popup appears: And from this choose Run diagnostics: Let the tool complete.
I got the following errors before the application failed (crashed) and then did not complete again if left it again and then To get around this issue, as the reset option to fix the AIP application in the diagnostics tool was not available due to the application crash, I followed the steps in http://social.technet.microsoft.com/wiki/contents/articles/19251.ad-rms-troubleshooting-reset-the-client-msipc.aspx to bootstrap the client manually.
If the AIP diag client completes, fix the listed issue or choose Reset in the client.
Once I had deleted the files and related registry keys mentioned in the above website I could restart any Office application.
The RMS certs, keys and settings where downloaded to the client again and the AIP client was able to protect a document where as before it was not: archive Exchange Server EXO IAmMEC Exchange Online Archive–Counting Archives.
April 5, 2016.
No Comments on Exchange Online Archive–Counting Archives.
If you are using Exchange Online Archive and what to get a count of the number of users with an archive, or a list of the users with an archive, then the following PowerShell scripts will give you this info: List all users with an Exchange Online Archive: Get-MailUser -ResultSize Unlimited | where {$_.
ArchiveName -ilike “In-Place Archive*”} Count all users with an Exchange Online Archive: (Get-MailUser -ResultSize Unlimited | where {$_.
ArchiveName -ilike “In-Place Archive*”}).
Count Both of these PowerShell cmdlets need to be run in Exchange Online via Remote PowerShell.
dirsync hybrid IAmMEC MSOL powershell Unable To Remove Office 365 Domain Error.
November 4, 2015.

Implementation Best Practices eBook
Tuesday September 08, 2020

Implementation Best Practices eBook. January 1, 2019. Tal Frankfurt. The purpose of this eBook is to share lessons learned and recommendations for best practices as you move forward with your implementation. These recommendations are not intended to be Salesforce specific but are rather globally applicable …

The post Implementation Best Practices eBook appeared first on betfair.

No Comments on Unable To Remove Office 365 Domain Error

If you need to remove a domain from Office 365 it needs to not be in use.
This includes the services that use that domain, for example an Accepted Domain in Exchange Online.
If though you have an expired, maybe test, Office 365 tenant and you want to remove a domain from it you may find unhelpful error messages.
For example I have seen in the domain removal process in the portal a message saying “Please don’t close this page while we remove your domain” etc.
It tries for several minutes as it predicts, but did not complete: Upon failing to complete you get a further warning before it finally gives up and tells you that it cannot complete: So the obvious next step (or obvious to me anyway) is to try the removal in remote PowerShell to Office 365.
The cmdlet is Remove-MsolDomain -DomainName domain.com but this comes back with with messages that might be helpful, but after repeated running of the cmdlet and fixing the error still suggests the same fix.
The error reads: Remove-MsolDomain : Unable to remove this domain.
Use Get-MsolUser -DomainName   to retrieve a list  of objects that are blocking removal.
The problem with this error is the list of objects here are only user accounts and not any of the other objects that could block a domain removal.
So sure, remove your unneeded users or change their UPN/email address to not include this domain that you want to remove, but also run Get-MsolContact and Get-MsolGroup and then remove or edit the contacts and the groups that use this domain.
So though the error says to fix the user objects that are blocking domain removal, you also need to fix or remove the groups and contacts as well.
2013 active directory Exchange Server Global Catalog IAmMEC iQ.
Suite Qualifications in Exchange Signatures.
October 2, 2015.
No Comments on Qualifications in Exchange Signatures.
In a recent project I was working with iQ.
Suite from GBS and specifically the component of this software that add signatures to emails.
The client are an international organization with users in different geographies and we needed to accommodate the users qualifications in their email signature.
The problem with this is that in Germany qualifications are written in front of the name and in the USA at the end and in other countries at the start and the end.
We were doing a Notes to Exchange migration and in Notes the iQ.
Suite signature software read data from Notes that was originally pulled from Active Directory, and so the client had placed the qualifications in the DisplayName field in the Active Directory.
But when we migrated to Exchange Server the Global Address List listed the users DisplayName an so the German users where all listed together with “Dipl” as the first characters of their name.
Also the name the email came from was written like this.
The signature worked, but the other changes that became apparent meant we had to work out a different way to look at this problem.
So rather than using DisplayName for the users name and qualifications, we used personalPrefix in Active Directory to store anything needed before their name (Dipl in the above German example, and Prof or Dr being English examples) and the generationQualifier Active Directory attribute to store any string that followed the users DisplayName (such as Jr in the USA or BSc for qualifications etc.) In iQ.
Suite we created a signature that looked like the following.
This has a conditional [COND] entry for personalTitle, displayName and generationQualifier.
That is if each of these are present, then show the displayName with personalTitle before it and generationQualifier after it.
If the user does not have values for these fields, do not show them.
The [COND] control is documented in iQ.
[COND]personalTitle;[VAR]personalTitle[/VAR] [/COND][COND]displayName;[VAR]displayName[/VAR][/COND][COND]generationQualifier; [VAR]generationQualifier[/VAR][/COND] What was not so well documented, and why I wanted to write this blog entry was that the personalTitle and generationQualifier attributes are not stored in the Global Catalog and so are missing in the users signature.
In the multi-domain deployment we had at the client, iQ.
Suite read the personalTitle, displayName and generationQualifier Active Directory attributes from the Global Catalog as Exchange was installed in a resource domain and the users in separate domains and so unless the attribute was pushed to the Global Catalog it was not seen by iQ.
To promote an attribute to be visible in the Global Catalog you need to open the Schema Management MMC snap-in, find the attributes of question and tick the Replicate this attribute to the Global Catalog field.
This is outlined in https://technet.microsoft.com/en-us/library/cc737521(v=ws.10).aspx.
Azure Azure Active Directory Group Policy IAmMEC password Password Writeback Errors.
July 7, 2015.
11 Comments on Password Writeback Errors.
I had been struggling with password writeback testing and was coming across the following set of errors, and found that searching for them uncovered nothing online.
So I wrote this blog to remind me and help you solve these issues.
These errors are all visible in the Application log of the Event Viewer.
User Restrictions.
The following error is because the user has “user cannot change password” option set in Active Directory: EventID 33004: TrackingId: 7344da2c-ab9d-42ef-adea-4a17d07fdeb9, Reason: Synchronization Engine returned an error hr=80230626, message=The password could not be updated because the management agent credentials were denied access., Context: cloudAnchor: User_9b83f544-ba22-4ffb-bff5-c1c2374d654c, SourceAnchorValue: F39SWQrM2EidaboN8UC8Ww==, UserPrincipalName: [email protected], Details: Microsoft.
PasswordResetException: Synchronization Engine returned an error hr=80230626, message=The password could not be updated because the management agent credentials were denied access.   at AADPasswordReset.
ThrowSyncEngineError(Int32 hr)   at AADPasswordReset.
ChangePassword(String cloudAnchor, String sourceAnchor, String oldPassword, String newPassword)   at Microsoft.
ChangePassword(String encryptedChangePasswordRequestString, String publicKeyEncryptedSymmetricKey, String publicKeyEncryptedSymmetricIV) And also, as the second error generated: Event ID 6329: An unexpected error has occurred during a password set operation.
“BAIL: MMS(5716): .\server.cpp(11139): 0x80230626 (The password could not be updated because the management agent credentials were denied access.)Azure AD Sync 1.0.8641.0″ Group Policy Restrictions.
Its possible that the errors you see for password writeback in the application log are due to restrictions on the user’s password that they have chosen.
If the password is not complex enough then you get a warning in the password reset page the user is visiting in Azure, but you can also get this is a Group Policy restriction is in place even if you have set a strong password.
The text in the error message in the Azure password change portal reads “This password does not meet your corporate password policy.
Please make sure to use a mix of upper and lowercase letters, numbers, symbols, and to update your password to one that you haven’t used previously.”.
Therefore though Azure accepted the passwords (original and new) the on-premises server rejected them with the following: Event ID 33008: TrackingId: 3c8c78dc-9167-4286-9384-e2f0e777af87, Reason: Synchronization Engine returned an error hr=80230619, message=A restriction prevents the password from being changed to the current one specified., Context: cloudAnchor: User_9b83f544-ba22-4ffb-bff5-c1c2374d654c, SourceAnchorValue: F39SWQrM2EidaboN8UC8Ww==, UserPrincipalName: [email protected], Details: Microsoft.
PasswordResetException: Synchronization Engine returned an error hr=80230619, message=A restriction prevents the password from being changed to the current one specified.   at AADPasswordReset.
ThrowSyncEngineError(Int32 hr)   at AADPasswordReset.
ChangePassword(String cloudAnchor, String sourceAnchor, String oldPassword, String newPassword)   at Microsoft.
ChangePassword(String encryptedChangePasswordRequestString, String publicKeyEncryptedSymmetricKey, String publicKeyEncryptedSymmetricIV) and Event ID 6329: An unexpected error has occurred during a password set operation.
“BAIL: MMS(5236): .\server.cpp(11139): 0x80230619 (A restriction prevents the password from being changed to the current one specified.)Azure AD Sync 1.0.8641.0″ This of course seems self explanatory – your password is not complex enough for your rules on-premises but complex enough to get past the Azure initial checks that it imposes.
This error though is especially annoying in test scenarios where you have turned off all the complexity checks.
To test why you are getting this error, first check its a password change error and not something else, and try and change the users password on-premises.
You should get the same restriction.
Then use the cmd prompt to check the password settings for the user.

TerrSet Geospatial Monitoring and Modeling Software
Tuesday September 08, 2020

PRODUCTS. PRODUCTS. Software Products for Geospatial Analysis Software Products for Geospatial Analysis. TerrSet Geospatial Monitoring and Modeling Software. TerrSet is an integrated geospatial software for monitoring and modeling the earth system The TerrSet software incorporates the IDRISI GIS Analysis and IDRISI Image Processing tools along …

The post TerrSet Geospatial Monitoring and Modeling Software appeared first on betfair.

net user username /domain

This will report the following: User name                    user1Full Name                    First LastCommentUser’s commentCountry/region code          000 (System Default)Account active               YesAccount expires              Never Password last set            7/7/2015 3:19:00 PMPassword expires             NeverPassword changeable          7/8/2015 3:19:00 PMPassword required            YesUser may change password     Yes Workstations allowed         AllLogon scriptUser profileHome directoryLast logon                   7/8/2015 10:31:05 AM Logon hours allowed          All Local Group MembershipsGlobal Group memberships     *Domain UsersThe command completed successfully.
In this example, notice the highlighted.
Here there password minimum age requirement in Group Policy has been removed: But the domain controller (after running gpupdate to force the change to the domain controller) still enforces a single day to allow the change to occur.
For test scenarios, modify group policy to 0 days (rather than not defined) and probably increase the max age from the suggested default of 30 days: After running gpupdate, you get the following for the net user command: Password last set            7/8/2015 10:42:05 AMPassword expires             NeverPassword changeable          7/8/2015 10:42:05 AM Now you should be able to change your password in Azure against an on-premises user.
Strong Password Required.
In the password change portal, the user is required to enter a strong password regardless of any restrictions that you have on-premises.
So even if you are testing and have removed all history and complex and renewal requirements for the password, Azure will ensure that a strong password of 7 or more characters is entered regardless of your on-premises policy.
In fact, Azure does not know your on-premises policy for password restrictions and enforces its own in addition to the one you have.
You get errors in the portal that read “Strong password required.
Combine at least three of the following: uppercase letters, lowercase letters, numbers, and symbols.”.
You also cannot reset the password to the same and the errors you get look like the following options:      Success.
For completion of the blog, here is what you should see in the event log when it is working: Event ID 31006: TrackingId: f430189d-984c-41d5-a4a6-333c66ffae1f, ChangePasswordRequestStart, Details: [email protected] Event ID 31007: TrackingId: f430189d-984c-41d5-a4a6-333c66ffae1f, ChangePasswordSuccess, Details: Context: cloudAnchor: User_9b83f544-ba22-4ffb-bff5-c1c2374d654c, SourceAnchorValue: F39SWQrM2EidaboN8UC8Ww==, UserPrincipalName: [email protected] 2008 2008 R2 2012 2012 R2 active directory ADFS 3.0 Azure Azure Active Directory cloud groups hybrid IAmMEC WAP Web Application Proxy windows Configuring Sync and Writeback Permissions in Active Directory for Azure Active Directory Sync.
July 3, 2015.
47 Comments on Configuring Sync and Writeback Permissions in Active Directory for Azure Active Directory Sync.
[Last updated 11th November 2019 – added support for Exchange Server automapping support, which was announced during Microsoft Ignite 2019 and will be supported in the first half of calendar year 2020.
This is supported by adding writeback for msExchDelegateListBL and msExchDelegateListLink attributes.
The below Exchange Hybrid writeback script has been updated to support these two attributes.] [This blog post was last updated 5th October 2017 – added support to Exchange Hybrid for msExchDelegateLinkList attribute which was announced at Microsoft Ignite 2017 for the support of keeping auto-mapping working cross on-premises and the cloud] [Updated 18th June 2017 in advance of the release of AADConnect version 1.1.553.0.
This post contains updates to the below scripts to include the latest attributes synced back to on-premises including publicDelegates, which is used for supporting bi-directional sync for "Send on Behalf” of permissions in Exchange Online/Exchange Server hybrid writeback scenarios] [U[Update March 2017 – added another blog post on using the below to fix permission-issue errors on admin and other protected accounts at http://c7solutions.com/2017/03/administrators-aadconnect-and-adminsdholder-issues] Azure Active Directory has been l ong the read-only cousin of Active Directory for those Office 365 and Azure users who sync their directory from Active Directory to Azure Active Directory apart from eight attributes for Exchange Server hybrid mode.
Not any more.
Azure Active Directory writeback is now available.
This enables objects to be mastered or changed in Azure Active Directory and written back to on-premises Active Directory.

This writeback includes: Devices that can be enrolled with Office 365 MDM or Intune

which will allow login to AD FS controlled resources based on user and the device they are on.
“Modern Groups” in Office 365 can be written back to on-premises Exchange Server 2013 CU8 or later hybrid mode and appear as mail enabled distribution lists on premises.
Does not require AAD Premium licences.
Users can change their passwords via the login page or user settings in Office 365 and have that password written back online.
Exchange Server hybrid writeback is the classic writeback from Azure AD and is the apart from Group Writeback is the only one of these writebacks that does not require Azure AD Premium licences.
User writeback from Azure AD (i.e.

Users made in Office 365 in the cloud for example) to on-premises Active Directory

Password Hash Sync (this is not really writeback, but its the only permission needed by default for forward sync, so added here).
Windows 10 devices for “Azure AD Domain Join” functionality.
All of these features require AADConnect and not and of the earlier verions.
You can add all these writeback functions from the AADConect setup wizard, and if you have used Custom mode, then you will need to implement the following permissions.
In all the below sections you need to grant permission to the connector account.
You can find the connector account for your Active Directory forest from the Synchronization Service program > Connectors > double-click your domain > select Connect to Active Directory Forest.
The account listed here is the connector account you need to grant permissions to.
SourceAnchor Writeback.
For users with (typically) multi-forest deployments or plans or a forest migration, the objectGuid value in Active Directory, which is used as the source for the attribute that keys your on-premises object to your synced cloud object – in AAD sync parlance, this is known as the SourceAnchor.
If you set up AADConnect version 1.1.553.0 or later you can opt to change from objectGuid to a new source anchor attribute known as ms-ds-consistencyGuid.
To be able to use this new feature you need the ability for AADConnect connector account to be able to read ObjectGUID and then write it back to ms-ds-consistencyGuid.
The read permissions are typically available to the connector account without doing anything special, and if AADConnect is installed in Express Mode it will get the write permissions it needs, but as with the rest of this blog, if you are not using Express Mode you need to grant the permissions manually and so write permissions are needed to the ms-ds-consistencyGuid attribute.
This can be done with this script.
$accountName = “domain\aad_account” #[t[this is the account that will be used by Azure AD Connect Sync to manage objects in the directory, this is often an account in the form of MSOL_number or AAD_number]br> $ForestDN = “DC=contoso,DC=com” $cmd = “dsacls ”$ForestDN” /I:S /G ”`”$accountName`”:WP;ms-ds-consistencyGuid;user”” Invoke-Expression $cmd | Out-Null $accountName = “domain\aad_account” #[t[this is the account that will be used by Azure AD Connect Sync to manage objects in the directory, this is often an account in the form of MSOL_number or AAD_number]br> $ForestDN = “DC=contoso,DC=com” $cmd = “dsacls ‘$ForestDN’ /I:S /G ‘`”$accountName`”:WP;ms-ds-consistencyGuid;user”” Invoke-Expression $cmd | Out-Null [/[/code] Note that if you use ms-ds-consistencyGuid then there are changes required on your ADFS deployment as well.
The Issuance Transform Rules for the Office 365 Relying Party Trust contains a rule that specifies the ImmutableID (aka AADConnect SourceAnchor) that the user will be identified as for login.
By default this is set to ObjectGUID, and if you use AADConnect to set up ADFS for you then the application will update the rule.
But if you set up ADFS yourself then you need to update the rule.
Issuance Transform Rules.
When Office 365 is configured to federate a domain (use ADFS for authentication of that domain and not Azure AD) then the following are the claims rules that exist out of the box need to be adjusted.
This is to support the use of ms-ds-consistencyguid as the immutable ID.
ADFS Management UI > Trust Relationships > Relying Party Trusts Select Microsoft Office 365 Identity Platform > click Edit Claim Rules You get two or three rules listed here.
You get three rules if you use -SupportMultipleDomain switch in Convert-MSOLDomainToFederated.
Rule 1: Change objectGUID to ms-DS-ConsistencyGUID   Rule Was: c:[T[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname”]gt; issue(store = “Active Directory”, types = (“http://schemas.xmlsoap.org/claims/UPN”, “http://schemas.microsoft.com/LiveID/Federation/2008/05/ImmutableID”), query = “samAccountName={0};userPrincipalName,objectGUID ;{1}”, param = regexreplace(c.
Value, “(?[^\\[^\\](?.+)”, “${user}”), param = c.
Value);   New Value:c:[Typ[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname”]; issue(store = “Active Directory”, types = (“http://schemas.xmlsoap.org/claims/UPN”, “http://schemas.microsoft.com/LiveID/Federation/2008/05/ImmutableID”), query = “samAccountName={0};userPrincipalName,ms-DS-ConsistencyGUID ;{1}”, param = regexreplace(c.
Value, “(?[^\\]+[^\\].+)”, “${user}”), param = c.
Value); Preparing for Device Writeback.
Device Writeback is used where you have an on-premises ADFS server farm and implement Conditional Access on-premises.
If you do cloud based authentication, including Pass-Through Auth (PTA) then you have no requirement for Device Writeback.
If you do not have a 2012 R2 or later domain controller then you need to update the schema of your forest.
Do this by getting a Windows Server 2012 R2 ISO image and mounting it as a drive.
Copy the support/adprep folder from this image or DVD to a 64 bit domain member in the same site as the Schema Master.
Then run adprep /forestprep from an admin cmd prompt when logged in as a Schema Admin.
The domain member needs to be a 64 bit domain joined machine for adprep.exe to run.
Wait for the schema changes to replicate around the network.
Import the cmdlets needed to configure your Active Directory for writeback by running Import-Module ‘C:\Program Files\Microsoft Azure Active Directory Connect\AdPrep\AdSyncPrep.psm1’ from an administrative PowerShell session.
You need Azure AD Global Admin and Enterprise Admin permissions for Azure and local AD forest respectively.

The cmdlets for this are obtained by running the Azure AD Connect tool

$accountName = “domain\aad_account” #[this [this is the account that will be used by Azure AD Connect Sync to manage objects in the directory, this is often an account in the form of MSOL_number or AAD_number]Initialize-ADSyncDeviceWriteBack -AdConnectorAccount $accountName -DomainName contoso.com #[domai[domain where devices will be created]In the domain partition you should now see an OU called RegisteredDevices.
The AADSync account now has permissions to write objects to this container.
In Azure AD Connect, if you get the error “This feature is disabled because there is no eligible forest with appropriate permissions for device writeback” then you need to complete the steps in this section and click Previous in the AADConnect wizard to go back to the “Connect your directories” page and then you can click Next to return to the “Optional features” page.
This time the Device Writeback option will not be greyed out.
Device Writeback needs a 2012 R2 or later AD FS server and WAP to make use of the device info in the Active Directory (for example, conditional access to resources based on the user and the device they are using).
Once Device Writeback is prepared for with these cmdlets and the AADConnect Synchronization Options page is enabled for Device Writeback then the following will appear in Active Directory: Not shown in the above, but adding the Display Name column in Active Directory Users and Computers tells you the device name.
The registered owner and registered users of the device are available to view, but as they are SID values, they are not really readable.
Preparing for Group Writeback.
Writing Office 365 “Modern Groups” back to Active Directory on-premises requires Exchange Server 2013 CU8 or later schema updates and servers installed.
To create the OU and permissions required for Group Writeback you need to do the following.
Import the cmdlets needed to configure your Active Directory for writeback by running Import-Module ‘C:\Program Files\Microsoft Azure Active Directory Connect\AdPrep\AdSyncPrep.psm1’ from an administrative PowerShell session.
You need Domain Admin permissions for the domain in the local AD forest that you will write back groups to.
The cmdlets for this are obtained by running the Azure AD Connect tool.
$accountName = “domain\aad_account” #[this [this is the account that will be used by Azure AD Connect Sync to manage objects in the directory, this is often an account in the form of MSOL_number or AAD_number]$cloudGroupOU = “OU=CloudGroups,DC=contoso,DC=com” Initialize-ADSyncGroupWriteBack -AdConnectorAccount $accountName -GroupWriteBackContainerDN $cloudGroupOU Once these cmdlets are run the AADSync account will have permissions to write objects to this OU.
You can view the permissions in Active Directory Users and Computers for this OU if you enable Advanced mode in that program.
There should be a permission entry for this account that is not inherited from the parent OU’s.
At the time of writing, the distribution list that is created on writeback from Azure AD will not appear in the Global Address List in Outlook etc.
or allow on-premises mailboxes to send to these internal only cloud based groups. To add it to the address book you need to create a new subdomain, update public DNS and add send connectors to hybrid Exchange Server.
This is all outlined in https://technet.microsoft.com/en-us/library/mt668829(v=exchg.150).aspx.
This ensure’s that on-premises mailboxes can deliver to groups as internal senders and not require external senders enabled on the group.
To add the group to the Global Address List you need to run Update-AddressList in Exchange Server.
Once group writeback is prepared for using these cmdlets here and AADConnect has had it enabled during the Synchronization Options page, you should see the groups appearing in the selected OU as shown: And you should find that on-premises users can send email to these groups as well.
Preparing for Password Writeback.
The option for users to change their passwords in the cloud and have then written back to on-premises (with multifactor authentication and proof of right to change the password) is also available in Office 365 / Azure AD with the Premium Azure Active Directory or Enterprise Mobility Pack licence.
To enable password writeback for AADConnect you need to enable the Password Writeback option in AADConnect synchronization settings and then run the following three PowerShell cmdlets on the AADSync server: Get-ADSyncConnector | fl name,AADPasswordResetConfiguration Get-ADSyncAADPasswordResetConfiguration -Connector “contoso.onmicrosoft.com – AAD” Set-ADSyncAADPasswordResetConfiguration -Connector “contoso.onmicrosoft.com – AAD” -Enable $true The first of these cmdlets lists the ADSync connectors and the name and password reset state of the connector.
You need the name of the AAD connector.
The middle cmdlet tells you the state of password writeback on that connector and the last cmdlet enables it if needed.
The name of the connector is required in these last two cmdlets.
To set the permissions on-premises for the passwords to be written back the following script is needed: $passwordOU = “DC=contoso,DC=com” #[you c[you can scope this down to a specific OU]untName = “domain\aad_account” #[this [this is the account that will be used by Azure AD Connect Sync to manage objects in the directory, this is often an account in the form of MSOL_number or AAD_number]$cmd = “dsacls.exe ”$passwordOU” /I:S /G ”`”$accountName`”:CA;`”Reset Password`”;user”” Invoke-Expression $cmd | Out-Null $cmd = “dsacls.exe ”$passwordOU” /I:S /G ”`”$accountName`”:CA;`”Change Password`”;user”” Invoke-Expression $cmd | Out-Null $cmd = “dsacls.exe ”$passwordOU” /I:S /G ”`”$accountName`”:WP;lockoutTime;user”” Invoke-Expression $cmd | Out-Null $cmd = “dsacls.exe ”$passwordOU” /I:S /G ”`”$accountName`”:WP;pwdLastSet;user”” Invoke-Expression $cmd | Out-Null Finally you need to run the above once per domain.
Preparing for Exchange Server Hybrid Writeback.
Hybrid mode in Exchange Server requires the writing back on eight attributes from Azure AD to Active Directory.
The list of attributes written back is found here.
The following script will set these permissions for you in the OU you select (or as shown at the root of the domain).
The DirSync tool used to do all this permissioning for you, but the AADSync tool does not.
Therefore scripts such as this are required.
This script sets lots of permissions on these eight attributes, but for clarify on running the script the output of the script is sent to Null.
Remove the “| Out-Null” from the script to see the changes as they occur (the script also takes a lot longer to run).
$accountName = “domain\aad_account” #[this [this is the account that will be used by Azure AD Connect Sync to manage objects in the directory, this is often an account in the form of MSOL_number or AAD_number]$HybridOU = “DC=contoso,DC=com” #Object type: user $cmd = “dsacls ”$HybridOU” /I:S /G ”`”$accountName`”:WP;proxyAddresses;user”” Invoke-Expression $cmd | Out-Null $cmd = “dsacls ”$HybridOU” /I:S /G ”`”$accountName`”:WP;msExchUCVoiceMailSettings;user”” Invoke-Expression $cmd | Out-Null $cmd = “dsacls ”$HybridOU” /I:S /G ”`”$accountName`”:WP;msExchUserHoldPolicies;user”” Invoke-Expression $cmd | Out-Null $cmd = “dsacls ”$HybridOU” /I:S /G ”`”$accountName`”:WP;msExchArchiveStatus;user”” Invoke-Expression $cmd | Out-Null $cmd = “dsacls ”$HybridOU” /I:S /G ”`”$accountName`”:WP;msExchSafeSendersHash;user”” Invoke-Expression $cmd | Out-Null $cmd = “dsacls ”$HybridOU” /I:S /G ”`”$accountName`”:WP;msExchBlockedSendersHash;user”” Invoke-Expression $cmd | Out-Null $cmd = “dsacls ”$HybridOU” /I:S /G ”`”$accountName`”:WP;msExchSafeRecipientsHash;user”” Invoke-Expression $cmd | Out-Null $cmd = “dsacls ”$HybridOU” /I:S /G ”`”$accountName`”:WP;msDS-ExternalDirectoryObjectID;user”” Invoke-Expression $cmd | Out-Null $cmd = “dsacls ”$HybridOU” /I:S /G ”`”$accountName`”:WP;publicDelegates;user”” Invoke-Expression $cmd | Out-Null $cmd = “dsacls ”$HybridOU” /I:S /G ”`”$accountName`”:WP;msExchDelegateLinkList;user”” Invoke-Expression $cmd | Out-Null $cmd = “dsacls ”$HybridOU” /I:S /G ”`”$accountName`”:WP;msExchDelegateListBL;user”” Invoke-Expression $cmd | Out-Null $cmd = “dsacls ”$HybridOU” /I:S /G ”`”$accountName`”:WP;msExchDelegateListLink ;user”” Invoke-Expression $cmd | Out-Null #Object type: iNetOrgPerson $cmd = “dsacls ”$HybridOU” /I:S /G ”`”$accountName`”:WP;proxyAddresses;iNetOrgPerson”” Invoke-Expression $cmd | Out-Null $cmd = “dsacls ”$HybridOU” /I:S /G ”`”$accountName`”:WP;msExchUCVoiceMailSettings;iNetOrgPerson”” Invoke-Expression $cmd | Out-Null $cmd = “dsacls ”$HybridOU” /I:S /G ”`”$accountName`”:WP;msExchUserHoldPolicies;iNetOrgPerson”” Invoke-Expression $cmd | Out-Null $cmd = “dsacls ”$HybridOU” /I:S /G ”`”$accountName`”:WP;msExchArchiveStatus;iNetOrgPerson”” Invoke-Exp.
Preparing for User Writeback.
[This [This functionality is not in the current builds of AADConnect]urrently in preview at the time of writing, you are able to make users in Azure Active Directory (cloud users as Office 365 would call them) and write them back to on-premises Active Directory.
The users password is not written back and so needs changing before the user can login on-premises.
To prepare the on-premises Active Directory to writeback user objects you need to run this script.
This is contained in AdSyncPrep.psm1 and that is installed as part of Azure AD Connect.
Azure AD Connect will install Azure AD Sync, which is needed to do the writeback.
To load the AdSyncPrep.psm1 module into PowerShell run Import-Module ‘C:\Program Files\Microsoft Azure Active Directory Connect\AdPrep\AdSyncPrep.psm1’ from an administrative PowerShell session.
$accountName = “domain\aad_account” #[this [this is the account that will be used by Azure AD Connect Sync to manage objects in the directory, this is an account usually in the form of AAD_number]$cloudUserOU = “OU=CloudUsers,DC=contoso,DC=com” Initialize-ADSyncUserWriteBack -AdConnectorAccount $accountName -UserWriteBackContainerDN $cloudUserOU Once the next AADSync occurs you should see users in the OU used above that match the cloud users in Office 365 as shown: Prepare for Password Hash Sync.
This set of PowerShell ensures that the AADConnect account has the correct permissions to read password hashes from the Active Directory when they are changed, so that the service can sync them to the cloud.
You need this permission whenever you enable Password Hash Sync (which could be in conjunction with another authentication method as well) $DomainDN = “DC=contoso,DC=com” $accountName = “domain\aad_account” #[this [this is the account that will be used by Azure AD Connect Sync to manage objects in the directory, this is often an account in the form of MSOL_number or AAD_number]$cmd = “dsacls.exe ”$DomainDN” /G ”`”$accountName`”:CA;`”Replicating Directory Changes`”;”” Invoke-Expression $cmd | Out-Null $cmd = “dsacls.exe ”$DomainDN” /G ”`”$accountName`”:CA;`”Replicating Directory Changes All`”;”” Invoke-Expression $cmd | Out-Null Prepare for Windows 10 Registered Device Writeback Sync.
Windows 10 devices that are joined to your domain can be written to Azure Active Directory as a registered device, and so conditional access rules on device ownership can be enforced.
To do this you need to import the AdSyncPrep.psm1 module.
This module supports the following two additional cmdlets to prepare your Active Directory for Windows 10 device sync: CD “C:\Program Files\Microsoft Azure Active Directory Connect\AdPrep” Import-Module .\AdSyncPrep.psm1 Initialize-ADSyncDomainJoinedComputerSync Initialize-ADSyncNGCKeysWriteBack These cmdlets are run as follows: $accountName = “domain\aad_account” #[this [this is the account that will be used by Azure AD Connect Sync to manage objects in the directory, this is often an account in the form of MSOL_number or AAD_number]$azureAdCreds = Get-Credential #[Azure[Azure Active Directory administrator account]C:\Program Files\Microsoft Azure Active Directory Connect\AdPrep” Import-Module .\AdSyncPrep.psm1 Initialize-ADSyncDomainJoinedComputerSync -AdConnectorAccount $accountName -AzureADCredentials $azureAdCreds Initialize-ADSyncNGCKeysWriteBack -AdConnectorAccount $accountName To successfully run these cmdlets you need to have the latest version of the Microsoft Online PowerShell modules installed (the V1.1 versions, not the V2.0 preview).
You can get these from https://www.powershellgallery.com/packages/MSOnline (which in turn needs MSOL Signin Assistant from https://www.microsoft.com/en-us/download/details.aspx?id=41950 and the Windows Management Framework v5 from https://www.microsoft.com/en-us/download/details.aspx?id=50395).
If you get errors in the above, make sure you have the correct version, download from above and try the scripts again.
Once complete, open Active Directory Sites and Services and from the View menu Show Services Node.
Then you should see the GUID of your domain under the Device Registration Configuration container.
ADFS ADFS 2.0 ADFS 3.0 IAmMEC MDM Mobile Device Management Multi-Factor Authentication OD4B ODFB OneDrive OneDrive For Business OWA for Devices Office 365 MDM (Mobile Device Management) From A Users Perspective.
June 17, 2015.

6 Comments on Office 365 MDM (Mobile Device Management) From A Users Perspective

The following list of steps and screenshots are taken during the enrolment process to add an iPhone and an Android phone to Office 365 once the free MDM solution that comes with Office 365 is enabled for the user.
Step Details Image from iPhone Image from Android 1.
Once your IT Administrator enables MDM for your Office 365 account you will get the following email on your device if you already have email configured.
It may take 24 hours from the admin configuring MDM for this to arrive.
Once this email arrives no further email will arrive from that account any device until the devices are enrolled with the company for management.
Click “Enrol your device” link in Step 1 of the email.
This will take you to the relevant app store of your device to install the Company Portal (iPhone as shown and Android devices).
Windows Phone users will see the Workplace Join settings (not shown)In the iOS example, the Company Portal app is already installed so we can click Open at the top.
For Android to the right, it shows that the app needs installing from the page they see in the App Store.
Once the app is installed you are required to login.
Enter your Office 365 username.
Upon entering your username you will either be directed to your network to login (if your company uses AD FS to login) or you enter the password here.
Step 4 shows the AD FS login page, which will probably have your company logo on it.
If your IT department does not use AD FS you enter your password here (the page will wait for you to enter it) 4.
This is an example AD FS login page with company logo.
If you are required to login with other information as well as your password you will be prompted for this as well.
Upon login being successful your device will start the enrolment process by connecting to both Office 365 and the device manufacturer to download required secure management info.
For iOS click Enroll to start the process.
For Android you need to click Activate.
The company you are enrolling your phone into will have some rights over some of the data on your phone – for example they will be able to remove the work email account from it if you leave the company.
Enrolment conditions will be enforced based on your companies requirement for using phones to access company data, for example a PIN number of a minimum length (see http://bit.ly/o365mdm for more on this) 7.
Enrolment goes through a series of steps with the screen changing a few times automatically.
Within a seconds you end up at the “Install” screen.
Click Install to add the management profile for the displayed company here.
Android and Windows Phone have less steps to go through.
A unique encryption key is generated for your device when using iOS devices.
For Android, you need to accept the compliance requirements configured by your administrator.
If you do not complete these requirements then business applications will not be available on the device.
You need to click install at the personal settings screen when using iOS devices.
For Android, once compliance requirements are set (in this case a PIN number is entered).
Note that for iOS, you have 1 hour to enter a PIN number to become compliant, but not for the Android.
You need to confirm that you trust this company for remote management of your device when using iOS devices.
For Android you need to name and install the certificate.
The management profile is installed and you can click Done when using iOS devices.
Device checks that it is enrolled and what the device settings are and if these settings are compatible with the companies required restrictions on the device.
On Android you may get a prompt about entering a PIN number or other compliance requirements if you did not enter them earlier   13.
Enrolment is confirmed.
Notice that my device(s) are displayed and my current device is not compliant with company policy (the red exclamation mark).
For Android devices, the My Devices tab will show your devices, including if there are any compliance issues.
Clicking my device in the Company Portal app shows the compliance status of the device.
Here the device is still checking compliance   15 And here the device is shown not to be compliant.
For Android devices not in compliance, it shows an Enrollment update available (if you did not meet compliance requirements during the Company App enrollment process) or if you are not compliance (for example device is not encrypted) then it will show that the device is not in compliance as shown.
16 Details on compliance state is iOS shows the “This device is not in compliance” message.
Further details on the compliance failure are shown under the message.
In this case the iOS device is unable to set up an email profile on the device and the Android devices need a longer password and device encryption 17 Clicking the “Unable to set up email on the device” message shows the full details.
In this case the device already has an email profile configured and for the iPhone this needs to be removed and the Company Portal will recreate it.
It is this recreated email profile that the iPhone/iPad can manage.
Android and Windows Phone users do not need to delete their email profile and have the device recreate it but Compliance requirements must still be met.
18 For the iPhone/iPad the steps to delete the existing profile are Settings > Mail, Contacts, Calendars > Click the email profile > click Delete Account For Android, if the device is compliant in the Company App then you need to check Exchange Server to validate this for you so that your email continues to work.
Back in the email program view the enrollment email as shown – click hyperlink #2 in the email and sign into the web based Device portal 19 Once the account is deleted on the iOS device it is not visible in the list of email accounts.
In this example the iCloud account remains along with two Exchange / Office 365 accounts that are not managed by MDM.
You can only have one MDM managed account per device at any given time.
Other compliance settings may be required such as a PIN number.
You have 60 minutes in iOS to enable this if required.
20 Once the Company App checks for compliance again and if you are compliant, a new email profile for your work appears.
Clicking it (called “Office 365 email”) requires entry of your password.
In Android, once the device is shown as compliant in #2 of the email, click the hyperlink for #3 in the email.
Click Allow on the certificate prompt if you see one.
21 You then see the email profile created.
Compare this to the image in Step 19 for the difference.
An Android, you will be informed that your device has successfully authenticated for email.
22 It is possible to rename the email profile.
In this case it is via Settings > Email, Contacts, Calendars > Office 365 email > Account and then change the “Description” value   23 Updated email profile listed   24 Email should now sync with your device again.
Notice that the email about needing to set up MDM is now missing and has been removed automatically.
On the Android, drag the Inbox screen down to refresh it and your emails will appear.
25 Now that the device is compliant (excepting the PIN number, which gives you 60 minutes of grace to complete this step) you can start other Office 365 aware applications.
Here we are going to sign into OneDrive and show our OneDrive for Business data 26 Your app requires a login 27 Which if you have an AD FS additional login you may also see   28 Your other app is now working, and in the case of OneDrive for Business did not need configuring   2013 IAmMEC Unable To Send Exchange Quota Message.
June 5, 2015.
No Comments on Unable To Send Exchange Quota Message.
In Exchange 2013 you can sometimes see the following event log error (MSExchange Store Driver Submission, ID 1012): The store driver failed to submit event mailbox MDB and couldn’t generate an NDR due to exception Microsoft.
InvalidSenderException   at Microsoft.
CopySenderTo(SubmissionItemBase submissionItem, TransportMailItem message)   at Microsoft.
GenerateNdrMailItem()   at Microsoft.
MailItemSubmitter.c__DisplayClass1.b__0()   at Microsoft.
RunUnderTableBasedExceptionHandler(IMessageConverter converter, StoreDriverDelegate workerFunction).
And this will be preceded by the following event log warning (MSexchangeIS, ID 1077): The mailbox on database is approaching its storage limit.
A notification has been sent to the user.
This warning will not be sent again for at least twenty four hours.
The mailbox in both errors is the same and it occurs for mailboxes that have moved to Exchange Server 2013 from Exchange Server 2010 and are close to their mailbox quota.
To fix the issue move the mailbox to a different database.
The easiest way to do this is New-MoveRequest where the same GUID is used.
If you have lots of these then this is a little more time consuming, unless you get PowerShell to the rescue.
The following two cmdlets will query the last seven days of the event logs for MSexchangeIS sourced events with ID 1077, get the event log message (which contains the mailbox guid), manipulate the string containing the message and generate a text file of just the mailbox guids.
The second cmdlet will run a New-MoveRequest for each mailbox listed in the text file.
Get-WinEvent -ComputerName PC1 -ProviderName MSExchangeIS | where {$_.
ID -eq 1077 -AND $_.
TimeCreated -gt [DateT[DateTime]
Date} | select @{Name=”mailbox” ;Expression={$_.
Substring(12,36)}} | ft -HideTableHeaders -AutoSize | out-file nearquota.txt and then Get-Content .\nearquota.txt | foreach {New-MoveRequest -Identity $_} Make sure though that your Application event log is large enough to store more than seven days of events and then run these cmdlets, per server every seven days until the issue goes away (or over the course of say a year, move all mailboxes to different databases and that fixes it as well).
Advanced Threat Protection ATP EOP Exchange Online Protection IAmMEC Safe Attachments Safe Links Advanced Threat Protection via PowerShell.
June 1, 2015.

3 Comments on Advanced Threat Protection via PowerShell

I discussed the newly released Advanced Threat Protection product in Office 365 on my blog, and in this article I want to outline the cmdlets that can be used to set this product up from Remote PowerShell to Office 365.
To connect to Office 365 via PowerShell take a search on your favourite search engine – there are lots and lots of articles on doing this.
Once you have a connection to Exchange Online and you have purchased the Exchange Online Advanced Threat Protection product, you can use PowerShell to do your administration and report gathering.
The cmdlets you can use are for Safe Links are: Disable-SafeLinksRule Enable-SafeLinksRule Get-SafeLinksPolicy Get-SafeLinksRule New-SafeLinksPolicy New-SafeLinksRule Remove-SafeLinksPolicy Remove-SafeLinksRule Set-SafeLinksPolicy Set-SafeLinksRule And the cmdlets you can use for Safe Attachments are: Disable-SafeAttachmentRule Enable-SafeAttachmentRule Get-SafeAttachmentPolicy Get-SafeAttachmentRule New-SafeAttachmentPolicy New-SafeAttachmentRule Remove-SafeAttachmentPolicy Remove-SafeAttachmentRule Set-SafeAttachmentPolicy Set-SafeAttachmentRule And for reporting, you can run Get-AdvancedThreatProtectionTrafficReport to report on the number of attachments blocked and the type of notification sent when looking at Safe Attachments.
Get-UrlTrace does the same report for Safe Links.
The cmdlet *-SafeLinksPolicy and *-SafeAttachmentPolicy controls the policy.
Every rule needs to be associated with a policy and so a policy needs creating first: New-SafeLinksPolicy “Protect C7 Solutions Users” Will create a Safe Link policy with the default settings.
This includes no URL tracking, no click through and is not enabled.
A better start might be New-SafeLinksPolicy “Protect C7 Solutions Users” -TrackClicks $true -IsEnabled $true -AllowClickThrough $false Once a policy is created, a rule can be added to that policy.
The *-SafeLinksRule and *-SafeAttachmentRule cmdlets control this in the shell.
You can only have one rule per policy.
An example cmdlet to create a rule would be: New-SafeLinksRule “Protect C7 Solutions Users” -SafeLinksPolicy “Protect C7 Solutions Users” -RecipientDomainIs “c7solutions.com” -Enabled $true Note that the –SafeLinksPolicy value matches that of the name of the previously created policy when making the rule.
To create a Safe Attachment policy and rule that protect all users by blocking malicious attachments and sending a report to an external mailbox you could use: New-SafeAttachmentPolicy “Protect C7 Solutions Users” -Enable $true -Redirect $true -RedirectAddress [email protected] –Action Block New-SafeAttachmentRule “Protect C7 Solutions Users” -RecipientDomainIs “c7solutions.com” -SafeAttachmentPolicy “Protect C7 Solutions Users” -Enabled $true The other cmdlets are self explanatory with regard to Enable- and Disable- and Set- and Remove-.
The advantage of using PowerShell to administer Safe Links and Safe Attachments is you can set up a policy in a lab and then copy it to a production environment or enable the same policy on many different tenants if you are a Microsoft Partner with customers interested in this advanced protection of their mailbox.
Advanced Threat Protection ATP EOP Exchange Online Protection IAmMEC malware proxy Safe Attachments Safe Links Getting Started with Office 365 Advanced Threat Protection.
June 1, 2015.

10 Comments on Getting Started with Office 365 Advanced Threat Protection

Announced a few months ago, Advanced Threat Protection became generally available on 1st June.
I have been involved with trialling this product during the beta and so I thought I would note down a few thoughts on setting this up and what to expect now that it is publicly available.
Advanced Threat Protection is an add-on product to Exchange Online/Exchange Online Protection with its own subscription, so you will not see these features and products unless you have subscribed.
Once you have subscribed you will get two new features in the Exchange Control Panel for Office 365.
These are the ability to find malware containing attachments before a detection signature for that malware exists (zero-day malware attacks) and the ability to filter all hyperlinks in email via a known malicious links service (filtering against spear-phishing attacks).
The feature to detect zero-day malware is called Safe Attachments and the feature to protect against spear-phishing is known as Safe Links.
Subscribing to Advanced Threat Protection.
After signing into the Office 365 administration portal click Purchase Services on the left hand menu and locate your current Office 365 subscription that contains Exchange Online or Exchange Online Protection (Office 365 Enterprise E3 contains EOP, so you would look for your suite purchase if you did not have a standalone purchase of EOP).
Your current subscriptions will contain the words Already Purchased underneath the item as shown: or In the two screenshots above you can see that you have no Exchange Online Advanced Threat Protection licences purchased.
To add Advanced Threat Protection licences click the Add more link and enter the number of licences you want to purchase.
You do not need to purchases the same number of licences as EOP or Exchange Online mailbox licences as you use the policy below to control who Advanced Threat Protection is available for.
Advanced Threat Protection for volume licence customers is available from August 2015 and for non-profit/educational licences from later in the year.
Once the purchase is confirmed the Advanced Threat’s menu entry appears in the Exchange Administration Console.
Also don’t forget to assign a licence to the appropriate users in the Office 365 portal.
Safe Attachments.
Safe Attachments in Advanced Threat Protection takes any email that meets the conditions of any one of the Safe Attachment policies that you create that also contains an attachment and checks this email for for malicious behaviour as it passes through Exchange Online Protection (EOP).
Before an email is checked by Safe Attachments the attachment has already been scanned for known malware and viruses.
So if the attachment contains malware that was not detected by an existing AV signature or if it is a safe attachment (no malware) then the email is routed to the Safe Attachments component in EOP.
If the email does not contain any attachments it is routed to the users mailbox by way of the other EOP spam filtering features.
Once an email is considered to have cause to be checked by the Safe Attachments component of ATP the individual attachments in the message are placed inside a newly created Windows virtual machine that is spun up in ATP for the purposes of this service.
The attachment is then executed or otherwise run (for example if it is a Word doc, it is opened in Word in the new VM that was created for it).
The VM is then watched for behaviour that is considered to be unsafe.
Examples of unsafe behaviour include setting certain known registry key locations (such as the RunOnce group of keys in Windows) or downloading malicious content from the internet.
If the attachment does not exhibit that behaviour then the email is released and sent on to the user.
If the email does exhibit these actions the email is not sent onward, and optionally a copy of the email in a form of a report is forwarded to an administrators mailbox (where care should be taken on opening the attachment).
The time it takes to spin up a new VM and execute the attachment is in the region of 7 to 10 minutes.
Therefore anyone subject to a Safe Attachments policy will have emails that contain attachments delayed by at least this amount of time.
Of course this delay is necessary to ensure that the recipient is not being sent malware that is currently not detected (zero-day attacks) and the impact of this delay needs to be considered against the benefit of the additional filtering that happens and the impact of that user executing the malware themselves on their own machine.
To protect a user with Safe Attachments you need to create a policy.
This is done in the Exchange Admin Centre in Office 365 and the “advanced threats” area as shown: In the above screenshot I have a single policy created called “Protect Brian Only”.
This would be an example where I wanted to protect those users whom I though where more likely to be subject to zero-day malware attacks – good examples would be highly targets accounts (CEO etc.), IT administrator/help desk accounts and of course the accounts of users who will click anything and so you are often cleaning up their PC.
There is no default policy, so unless a user is protected by a policy that you the administrator create, they are not subject to the Safe Attachments feature.
As Advanced Threat Protection is an additional licence, only those users who are licenced should be included in any policy.
Opening the “Protect Brian Only” example policy above shows me three sets of options.
These are:    The first page allows me to edit the name and description.
The second page sets the policy (more on this below) and the final page sets who the policy applies to.
In this example it applies to a single recipient who was selected from the list of users in Office 365, though it could be a list of more than one user or anyone with a given email domain or anyone in an already created group.
The policy setting allows me to do the following: Scan attachment containing emails (with options to not do this scanning, scan and send onward to the user regardless of the result, block the emails containing bad attachments or replace the attachments with a notification but allow the contents of the email to go on through).
Redirect the attachment containing emails to an alternative email address and what address to use.
This is great for seeing what is blocked and acting as a sort of reporting service.
Warning – this email address will get malicious emails sent to it, handle with extreme care.
Finally, in the event of a timeout at EOP/ATP where the attachment cannot be scanned in 30 minutes, check this box to treat the attachment in the same way as malicious emails are treated.
This is the default action.
In the mailbox of the intended recipient, if block or replace is selected in the policy then the user will not see the malicious attachment and therefore cannot accidently execute its contents.
In the mailbox of the email address used for the redirection, you will see messages such as follows: Here you see a report email that contains the email that was detected as malicious.
You can see the To: address (redacted in the graphic above) and that it was not sent to the intended recipient and that it should not be opened.
All in all, its a very simple and inexpensive way to protect the mailboxes of either all staff or those you consider subject to targeted malware such as CEO type staff and the IT department.
Even if you do not redirect emails containing malicious attachments, you can report on the number and type of attachments that are blocked from the reporting console available from the icon on the ATP toolbar.
The following shows a 30 day report for my tenant (which has only a few live mailboxes protected).
For data-points beyond 7 days old it will take a short while for the information on the report to be returned to you and you need to request that report from the provided link.
For data-points under 7 days you can see the information in real-time.
The grey background to report shows where the 7 day period is located.
In the below screenshot the above malware can be see in the report as the single instance of an email that passed AV scanning successfully but was in fact a zero-day attack.
The second screenshot below shows the type of malware attachments that ATP is blocking.
From this we can see that the risk lies in maliciously crafted Excel and Word attachments.
Safe Links.
When an email is delivered to the end recipient, any technology that checks the target of any link in the email is prone to one large issue – the web page or attachment on the other side of the hyperlink in the email may be safe and okay to view at the time of delivery, but might not be at the time the user comes to open the email and then click the link.
Being aware of users working, or at least email reading hours, and delivering emails outside this timeframe with links to websites that are okay at the time of delivery means the email passes any web site or download checks done by the email server.
Advanced Threat Protection’s Safe Links feature protects the user by rewriting the hyperlink in the email body so that the link is checked at the point of click and not the point of delivery.
To do this the hyperlink is changed from the target to the Safe Links portal.
Then when the user clicks the link, they are taken to the Safe Links portal and if the site is now on a block list, the user is blocked, but if the target of the link is fine they are sent a browser redirect to the original target.
Note that this is not a proxy server – you do not connect to the target URL through the Safe Links portal, you just visit the Safe Links portal when you click the link and if the target is safe at point of click you are directed via your browser to the target (a client side redirect).
If the target is not safe at point of click then an error page is displayed.
In the following screenshot is an email with a hyperlink in it.
This link was received by me to my Safe Links protected account and it looks link it might be an attempt to download malware to my computer, but I am going to click the link anyway (in second screenshot I am hovering over the hyperlink):   You can see from the above screenshot that the hyperlink takes the user first to https://na01.safelinks.protection.outlook.com/?url=targetURL&data=value&sData=otherValue.
The na01 part of the URL will be regionally specific and so might read emea01 or apac01 etc.
When the user clicks the link they go to region.safelinks.protection.outlook.com.
In my case I see the following webpage: Here I am told the page has been classified as malicious.
I also have an option to continue anyway (and I can control if this setting appears for users or not) and an option to close the browser window.
If the hyperlink is not malicious at the point of click then I still go to the Safe Links portal (as it is the portal that checks the link at point of click), but then get redirected to the target URL.
This can be seen in the following screenshot which shows the F12 developer tools enabled in the browser and the network trace screen shown at the bottom of the window: You will see that the first line is the Safe Links portal and this take 0.75 second before being redirected with a HTTP 302 client side redirect to the target URL and then the rest of the objects on the target page (until I paused the trace).
So how do I set this all up.
It is very similar to the Safe Attachments above in that we create a policy, and then any email that contains hyperlinks that is delivered to the end user after that users is added to a policy get rewritten.
First we go to the Advanced Threats area of the Exchange Administration Console: Here you can see an existing policy.
There are no policies by default.
If I create a new policy I need to provide the following: You can see from the screenshot that you need a name for the policy and whether or not a link is rewritten (policies with greater priority take precedence, so if a user is subject to two or more polices then only the higher priority policy takes effect, therefore you can use a policy to turn off link rewriting for a subset of users covered under a lower policy that enabled it for more users).
Also you can disable link tracking and not to allow users to have the option to click through to the target URL.
Link tracking allows you to report who clicked what link and not allowing users to click through disables the “Continue to this website (not recommended)” link on the Safe Links warning page.
You also have the ability to control URL’s that you do not want to rewrite, and rewriting will only happen for FQDN URL’s (that is those with dots in them) and not single name URL’s such as http://intranet.  This allows you to bypass redirection for sites you know are safe or are FQDN’s but are internal.
Finally you get to set who the policy applies to.
You do not need to apply the policy to all users if you have not licenced all users, but you can set policy based on who the recipient is, what domain the recipient is in (all users in that domain) or a group (some users).
On the Mail Flow menu in Exchange Control Panel you can view a URL Trace of the links that users have clicked in the past 7 days.
The report shows you the link clicked and if it was blocked or not.
If the click through option is enabled, it will show if that was done as well.
Only users in policies that track clicks will be reported.
As report looks like the following: Further Administration.
To administer your Safe Links and Safe Attachments policy and rules via Remote PowerShell see http://c7solutions.com/2015/06/advanced-threat-protection-via-powershell Azure cloud groups IAmMEC mcm mcsm MVP powershell Managing Office 365 Groups With Remote PowerShell.
May 12, 2015.

2 Comments on Managing Office 365 Groups With Remote PowerShell

Announced during Microsoft Ignite 2015, there are now PowerShell administration cmdlets available for the administration of the Groups feature in Office 365.
The cmdlets are all based around “UnifedGroups”, for example Get-UnifiedGroups.
Create a Group Use New-UnifiedGroup to do this.
An example would be New-UnifiedGroup -DisplayName “Sales” -Alias sales –EmailAddress [email protected] The use of the EmailAddress parameter is useful as it allows you to set a group that is not given an email address based on your default domain, but from one of the other domains in your Office 365 tenant.
Modify a Groups Settings Use Set-UnifiedGroup to change settings such as the ability to receive emails from outside the tenant (RequireSenderAuthenticationEnabled would be $false), limit email from a whitelist (AcceptMessagesOnlyFromSendersOrMembers) and other Exchange distribution list settings such as hidden from address lists, mail tips and the like.
AutoSubscribeNewMembers can be used to tell the group to email all new messages to all new members, PrimarySmtpAddress to change the email address that the group sends from.
Remove a Group This is the new Remove-UnifiedGroup cmdlet.
Add Members to a Group This cmdlet is Add-UnifiedGroupLinks.
For example Add-UnifiedGroupLinks sales -LinkType members -Links brian,nicolas will add the two names members to the group.
The LinkType value can be members as shown, but also “owners” and “subscribers” to add group administrators (owners) or just those who receive email sent to the group but not access to the groups content.
To change members to owners you do not need to remove the members, just run something like Add-UnifiedGroupLinks sales –LinkType owners -Links brian,nicolas You can also pipe in a user list from, for example a CSV file, to populate a group.
This would read: Add-UnifiedGroupLinks sales -LinkType members -Links $users where $users = Get-Content username.csv would be run before it to populate the $users variable.
The source of the variable can be anything done in PowerShell.
Remove Members from a Group For this use Remove-UnifiedGroupLinks and mention the group name, the LinkType (member, owner or subscriber) and the user or users to remove.
To Disable Group Creation in OWA Set-OWAMailboxPolicy is used to create a policy that is not allowed to create Groups and then users have that policy applied to them.
For example Set-OWAMailboxPolicy “Students” –GroupCreationEnabled $false followed by Set-CASMailbox mary –OWAMailboxPolicy Students to stop the user “mary” creating groups.
After the policy is assigned and propagates around the Office 365 service, the user can join and leave groups, but not create them.
Control Group Naming This feature allows you to control the group name or block words from being used.
This is easier to set in the Distribution Groups settings in Exchange Control Panel rather than via PowerShell.
To do this EAC use Recipients > Groups and click the ellipses icon (…) and select Configure Group Naming Policy.
This is the same policy for distribution groups.
You can add static text to the start or end of name, as well as dynamic text such as region.
Admins creating groups are not subject to this policy, but unlike DL’s if they create groups in PowerShell the policy is also not applied and so the -IgnoreNamingPolicy switch is not required.
ADFS app password Azure IAmMEC MFA multi-factor auth Multi-Factor Authentication How To Change Your Office 365 App Password.
March 19, 2015.
12 Comments on How To Change Your Office 365 App Password.
If you are enabled for Multi-Factor Authentication (MFA) in Office 365 then you will need an App Password for some applications that do not support MFA.
The user interface for creating a new App Password is well hidden in Office 365 (its not on the Password page for example).
Post updated in 2016 to take account of the changes in the Office 365 portal.
Post updated in 2017 to show that Microsoft have added a short URL to reach this page.
You can skip the below and go to http://aka.ms/CreateAppPassword Post updated in Aug 2018 to take consideration of the new SSPR and MFA converged UI.
If you have this turned on then App Password changes are as described at https://docs.microsoft.com/en-gb/azure/active-directory/user-help/security-info-app-passwords.
If you have not enabled this yet (late 2018 it will probably become the default regardless) then the above link will work for you.
Here is how to find it now: The user logs into Office 365 portal (http://portal.office.com) and clicks their photo to the top-right of the page.
Click My Account.
Click Security and Privacy menu to the left or the Manage Security and Privacy link on the main area of the page.
Click Additional Security Verification.
Click Create and manage app passwords.
This takes you to https://account.activedirectory.windowsazure.com/AppPasswords.aspx.
You can (and therefore should) bookmark this page now so you don’t need these instructions again!.
Create yourself an additional app password and give it a description.
Use the new app password in the program that you need to login to.
Here is how to find it (in the old Office 365 portal) The user logs into Office 365 portal (http://portal.office.com) and clicks the cog icon to the top-right of the page.
Click Office 365 Settings.
Scroll down past Password and choose Additional Security Verification.
Click Update my phone numbers used for account security.
Answer your phone to approve your request to go to this page (you might not be asked for this).
Click “app passwords” on the top menu.
This takes you to https://account.activedirectory.windowsazure.com/AppPasswords.aspx.
You can (and therefore should) bookmark this page now so you don’t need these instructions again!.
Create yourself an additional app password and give it a description.
Use the new app password in the program that you need to login to.
2013 Azure IAmMEC MFA MVP smartphone Exchange OWA and Multi-Factor Authentication.
January 14, 2015.
21 Comments on Exchange OWA and Multi-Factor Authentication.
This article is now out of date Multi-factor authentication (MFA), that is the need to have a username, password and something else to pass authentication is possible with on-premises servers using a service from Windows Azure and the Multi-Factor Authentication Server (an on-premises piece of software).
The Multi-Factor Authentication Server intercepts login request to OWA, if the request is valid (that is the username and password work) then the mobile phone of the user is called or texted (or an app starts automatically on the phone) and the user validates their login.
This is typically done by pressing # (if a phone call) or clicking Verify in the app, but can require the entry of a PIN as well.
Note that when the MFA server intercepts the login request in OWA, there is no user interface in OWA to tell you what is happening.
This can result in user disconnect and stops the use of two-way MFA (receive number by text, type number into web application type scenario).
Therefore to that end, .

MFA directly on the OWA application is not supported by the Microsoft Exchange team

Steps for setting up ADFS for Exchange Server 2013 SP1 or later are at https://technet.microsoft.com/en-us/library/dn635116(v=exchg.150).aspx.
Once this is in place, you need to enable MFA for ADFS rather than MFA for OWA.
I have covered this in a separate post at http://c7solutions.com/2016/04/installing-azure-multi-factor-authentication-and-adfs.
To configure Multi-Factor Authentication Server for OWA (unsupported) you need to complete the following steps: Configure MFA in Azure (see http://c7solutions.com/2015/01/windows-rras-vpn-and-multi-factor-authentication for the steps on setting this up).
Install the MFA server on-premises.
Configure and test users for MFA (see http://c7solutions.com/2015/01/windows-rras-vpn-and-multi-factor-authentication as well for these steps).
Integrate MFA into OWA.
Some of these steps are the same regardless of which service you are adding MFA to and some slightly different.
I wrote a blog on MFA and VPN at http://c7solutions.com/2015/01/windows-rras-vpn-and-multi-factor-authentication and this contains the general setup steps and so these are not repeated here.
Just what you need to do differently Step 1.
See http://c7solutions.com/2015/01/windows-rras-vpn-and-multi-factor-authentication Step 2: Install MFA Server on-premises.
This is covered in http://c7solutions.com/2015/01/windows-rras-vpn-and-multi-factor-authentication, but the difference with OWA is that it needs to be installed on the Exchange CAS server where the authentication takes place.
Ensure you have.
NET 3.5 installed via Server Manager > Features.
This will install the.
NET 2.0 feature that is required by MFA server.
If the installation of the download fails, this is the most likely reason for the failure, so install.
NET 3.5 and then try the MFA Server install again.
The install of the MFA server does not take very long.
After a few minutes the install will complete and then you need to run the Multi-Factor Authentication Server admin tools.
These are on the Start Screen in More Apps or the Start Menu.
Note that it will start the software itself if given time: Do not skip the wizard, but click Next.
You will be asked to activate the server.
Activating the server is linking it to your Azure MFA instance.
The email address and password you need are obtained from the Azure multi-factor auth provider that was configured in Step 1.
Click the Generate Activation Credentials on the Downloads page of the Azure MFA provider auth management page.
The credentials are valid for ten minutes, so your will differ from mine.
Enter them into the MFA Server configuration wizard and click Next.

MFA Server will attempt to reach Azure over TCP 443

Select the group of servers that the configuration should replicate around.
For example, if you where installing this software on each Exchange CAS server, then you might enter “Exchange Servers” as the group name in the first install and then select it during the install on the remaining servers.
This config will be shared amongst all servers with the same group name.
If you already have a config set up with users in it and set up a new group here, then it will be different settings for the users.
For example you might have a phone call to authenticate a VPN connection but use the app for OWA logins.
This would require two configs and different groups of servers.
If you want the same settings for all users in the entire company, then one group (the default group) should be configured.
Next choose if you want to replicate your settings.
If you have more than one MFA Server instance in the same group select yes.
Then choose what you want to authenticate.
Here I have chosen OWA: Then I need to choose the type of authentication I have in place.
In my OWA installation I am using the default of Forms Based Authentication, but if you select Forms-based authentication here, the example URL for forms based authentication shown on the next page is from Exchange Server 2003 (not 2007 or later).
Therefore I select HTTP authentication Next I need to provide the URL to OWA.
I can get this by browsing the OWA site over https.
The MFA install will also use HTTPS, so you will need a certificate and have this trusted by a third party if you want to support user managed devices.
Users managing their own MFA settings (such as telephone numbers and form of authentication) reduces the support requirement.
That needs the User Portal, the SDK and the Mobile App webservice installed as well.
These are outside the scope of this blog.
For here I am going to use https://servername/owa.
Finish the installation at this time and wait for the admin application to appear.
Step 3: Configure Users for MFA.
Here we need to import the users who will be authenticated with MFA.
Select the Users area and click Import from Active Directory.
Browse the settings to imports group members, or OUs or a search to add your user account.
Once you have it working for yourself, add others.
Users not listed here will not see any change in their authentication method.
Ensure that your test user has a mobile number imported from the Active Directory.
If not add one, choosing the correct country code as well.
The default authentication for the user is that they will get a phone call to this number and need to press # before they can be logged in.
Ensure that the user is set to Enabled as well in the users area of the management program.
Step 4: Configure OWA for MFA (additional steps).
On the IIS Authentication node you can adjust the default configuration for HTTP.
Here you need to set Require Multi-Factor Authentication user match.
This ensures that each auth attempt is matched to a user in the users list.
If the user exists and is enabled, then do MFA for them.
If disabled, then the setting for Succeed Authentication on the advanced tab comes into play.
If the user is not listed, authentication passes through without MFA.
Change to the Native Module tab and select OWA under Default Web Site only.
Do not set authentication on the Backend Web Site.
Also enable the native module on ECP on the Default Web Site as well: Then I can attempt a login to OWA or ECP.
Once I successfully authenticate my phone rings and I am prompted to press #.
Once I press # I am allowed into Exchange.
Posts navigation.
← Newer Posts 1 2 3 Older Posts → Select Category 2003 2004 2007 2008 2008 R2 2010 2012 2012 R2 2013 2016 2019 2FA 64 bit AADConnect aadrm AADSync access acdc active directory activesync add-in ADDS ADFS ADFS 2.0 ADFS 3.0 ADFS Connector AdminSDHolder adsiedit Advanced Threat Protection agent AIP android antivirus anycast app password Application Guard archive asterisk asterisknow ATP Authentication autodiscover autodiscover v2 az Azure Azure Active Directory Azure AD Azure Information Protection AzureAD backup baseline bing bios booking bpos branding cafe calendar certificates Chrome citrix Click To Run Click2Run cloud Cloud PBX Clutter cmak compliance conditional access conversation crm cross-forest cyber bullying dell Deployment device device registration dirsync dkim DLP dmarc DNS domain door download draytek DSC duplicate dynamic delivery Dynamics EAS ebs 2008 Edge EM+S email encryption Endpoint Manager enterprise mobility + security Entourage EOP    Exchange Online Protection error EWS exchange exchange online Exchange Server EXO ExpressRoute federation FIDO firewall Focused Inbox FOPE Free/Busy GeoDNS Global Catalog GPO Group Policy groups hosting hotfix https hybrid hyper-v IAmMEC IFilter iis illustration install Intune iOS ip iPad iPhone ipsec ipv4 ipv6 iQ.
Suite IRM isa ISA Server 2004 ISA Server 2006 JetNexus journal journaling Kemp kerberos lab licence Live Event load balancer Load Master loadbalancer logo Lync Server mailbox malware management mcafee mcas mcm mcsm mdatp MDM media player MFA microsoft Microsoft 365 Microsoft Cloud App Security Microsoft Defender Advanced Threat Protection Microsoft Teams migration Mobile Device Management mobile phones modern authentication monthly channel move msExchDelegateListBL msExchDelegateListLink MSOL multi-factor auth Multi-Factor Authentication MVP MX ndr Netscaler networking NTL OAuth OD4B ODFB off offensive Office Office 365 Office 365 Advanced Threat Protection Office 365 Groups Office 365 ProPlus oledb OneDrive OneDrive For Business openmanage orange organization relationships osma Outlook owa OWA for Devices password paxton pbx permissions PFDAVAdmin phish phishing phone factor pkcs pki places policy powershell pptp preview Proof Of Concept proxy pst PSTN PSTN Conferencing Public Folders recovery remote desktop remote web workplace retention retention policies rms room router rras rtp rules rww Safe Attachments Safe Documents Safe Links Salesforce sbs 2008 SCOM sdk search security Security and Compliance Center self-service password reset semi-annual channel send-on-behalf server administrator server core shared mailbox sharepoint sip Skype For Business Online Skype for Business Server smarthost smartphone sms smtp spam spf spoof spv SQL sql express SSL SSO sspr sstp starttls storage card Stream supervision sync error sysprep Teams TechEd terminal server Terminal Services text message Threat Management TLS tmg token2 transport transport agent ts gateway Uncategorized unif unified messaging update upgrade vc++ vhd virtual pc virtual server virtualisation vista visual studio vm VNet Voicemai voicemail.

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *