Get-Azure
Description
The Get-AzureADSubscribedSku cmdlet gets subscribed SKUs to Microsoft services.
Getting Started with OptinMonster and WordPress Checklist
To get the most out of OptinMonster, we’ve put together the following checklist to guide you through creating your first campaign.
- Create your first campaign.
- Connect your campaign to Google Analytics so you can immediately track impressions and conversions – Note: this step is required for access to any campaign statistics.
- Install the OptinMonster Plugin on your WordPress site.
- Configure the Output Settings for your campaign to control where it loads on your site.
Advanced
When you’re ready to take your campaign to the next level:
- Split-Testing your campaign helps you improve conversions by testing different colors, copy, configuration settings and more.
- Page Level Targeting: For more advanced page targeting you can use Google Tag Manager to control when and where on your site the campaign appears.
- Cookie Configuration: OptinMonster makes it easy to set both individual and global cookies, controlling how often visitors see your campaign.
- MonsterLinks: You can show your campaign with the click of a link or button on your site with MonsterLinks.
- Downloadable File Delivery: There are many ways you can deliver downloadable content when using OptinMonster.
- Yes/No Campaigns: If you don’t want to collect email addresses you can easily the default form to a yes/no campaign instead.
- Privacy Policy: Add a privacy policy to your campaign.
- Mobile: Create a mobile campaign to show to mobile visitors.Note: mobile options require a Pro subscription.
Azure Identity Protection – Enterprise Mobility + Security
Azure Identity Protection
Azure Identity Protection is a feature of Microsoft Enterprise Mobility + Security and is a premium feature in EMS E5. We conducted a test to see if a user would be blocked while trying to log in from 2 separate locations.
We went to https://portal.azure.com/ and logged in with credentials normally from our home office server. I then created a 2012 Server virtual machine setting up and configuring Active Directory and azure AD Connect.
Using the Tor browser I went to portal.azure.com to login with the same user a 2nd time.
Our Results
Your sign-in was blocked
We’ve detected something unusual about this sign-in.
For example, you might be signing in from a new location, device, or app.
Before you can continue, we need to verify your identity. Please contact your admin.
After viewing more details we get a better picture of what scenario is; at this point to see that the user has tried to sign in a second time from an unknown location and has been blocked.
We can see from the message the sign-in was blocked.
Your sign-in was blocked
We’ve detected something unusual about this sign-in. For example, you might be signing in from a new location, device, or app.
Before you can continue, we need to verify your identity. Please contact your admin.
Sign out and sign in with a different account
We will now create a sign-in risk policy. Login to portal.azure.com -> Azure AD Identity Protection ->Sign-in risk policy
Risky sign-ins
Azure Active Directory detects risk event types in real-time and offline.
Each risk event that has been detected for a sign-in of a user contributes to a logical concept called risky sign-in.
A risky sign-in is an indicator of a sign-in attempt that might not have been performed by the legitimate owner of a user account.
Running Docker first time on macOS High Sierra
Docker CE macOS
Docker CE for Mac is an easy-to-install desktop app for building, debugging, and testing Dockerized apps on a Mac. Docker for Mac is a complete development environment deeply integrated with the Mac OS Hypervisor framework, networking, and filesystem. Docker for Mac is the fastest and most reliable way to run Docker on a Mac.
When the installation completes and Docker starts, the whale in the top status bar shows that Docker is running, and accessible from a terminal.
Run it
Open a command-line terminal (I’m using Iterm-2), we’ll try some Docker command
Run docker version to check that you have the latest release installed.
Run docker run hello-world to verify that Docker is pulling images and running as expected.
To learn more, read the Docker for Mac documentation
Azure: Fix Unhealthy Identity synchronization
Azure: Fix Unhealthy Identity synchronization. Yesterday I was in my office 365 portal, just checking an account, when I logged in I was presented with this message “Unhealthy Identity synchronization” on the office 365 portal admin homepage. You may see something like this in your office 365 portal if there is a Sync issue or some other problem with Azure AD Connect. I also received an email about an unhealthy sync. See snapshot of the email.
Subject: Unhealthy Identity synchronization Notification
As you can see below from the image, we haven’t had a directory sync for the last 54 hours.
Last directory sync Warning: last synced 54 hours ago
We will have to click on the link and see what the particular error is reporting with our Azure AD Connect Synchronization or use the link to troubleshoot our error.
Fixing problems with directory synchronization for Office 365
Ok, time now to review the version of AD Connect we are running on our local Active Directory and do a in-place upgrade to solve this issue, often times upgrading the AD Connect Sync client will resolve issues with the synchronization. Let see what’s the current version and what version we are running on our member server and see if we need to do the in-place upgrade.
The current version is 1.1.561.0 so there must be another issue going on, at this point we’ll try and run a few Power Shell Commands to push a sync. We will run
Start-ADSyncSyncCycle -PolicyType Initial - To push an initial sync over to office 365.
At this point when we ran the command we got a message back stating the sync was busy.
We also ran this command to see the health of the sync:
Get-ADSyncConnectorRunStatusSo we then opened to the Synchronization Scheduler to check the connectors, stopped them and ran a full synchronization, after that we restarted the member server.
This eventually cleared up our sync issue and from the portal we can see a healthy sync.
A great link you can use to troubleshoot your AD Connect Sync; also you may want to keep an eye on your syncs using the Azure AD Connect Health Dashboard that comes with Azure Active Directory Premium.