Faraday and Microsoft Reports Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Keep Faraday and Microsoft Reports matched by integrating their events and actions. When analytics events happen in Faraday, update the Microsoft Reports automatically - without any line of code in visual workflow builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Faraday and Microsoft Reports

Detailed info you need to know about Faraday and Microsoft Reports integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Faraday

    • Analytics
    • 1 trigger
    • 62 searches
    • 87 actions

    Predictive analytics that forecasts customer behavior from your data.[5]

  • Microsoft Reports

    • Analytics
    • 7 searches
    • 1 action

    Microsoft Graph reports for directory and usage analytics.[6]

How to connect Faraday to Microsoft Reports

Set up your Faraday and Microsoft Reports integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Faraday and Microsoft Reports work in WEXTL?

WEXTL exposes actions and triggers for Faraday and Microsoft Reports that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Faraday triggersMicrosoft Reports actions

Faraday modules

  • Watch Events Runs the workflow the moment Faraday sends a webhook event, passing its Type, Timestamp, Account ID, Resource Type and Resource ID.
  • Add an Upload Stores the content of File in your Faraday uploads, such as a CSV, and returns the Subpath and Size of the new upload.
  • Archive a Cohort Marks a cohort as archived and returns its Status. Use Cascade To to list dependent resource IDs that go into the archive with it.
  • Archive a Connection Archives a connection to outside data and returns its Created at time.
  • Archive a Dataset Puts a dataset into the archive. Use Cascade to All to include everything that depends on it.
  • Archive a Forecast Archives a forecast and returns its ID, Name and Status.
  • Archive a Persona Set Marks a persona set as archived. The reply shows its Name and Status.
  • Archive a Recommender Files a recommender in the archive. Use Cascade to All to bring its dependent resources along.
  • Archive a Scope Archives a scope. The Created at time is returned.
  • Archive a Stream Puts a data stream into the archive. The Status of the stream is returned.
  • Archive a Target Archives a target. Use Cascade To to list the dependent IDs that should be archived alongside it.
  • Archive a Trait Archives a trait, returning its Name together with its Account id.
  • Archive an Atlas Archives an atlas. Use Cascade to All to also archive the resources that depend on it, or Cascade To to name the dependent IDs.
  • Archive an Outcome Sets an outcome aside in the archive. Use Cascade To to list the dependent IDs that should be archived in the same step.
  • Create a Cohort Defines a cohort of people from Stream Conditions (JSON), Place Conditions (JSON), Location Conditions (JSON), Traits (JSON) or Attributes (JSON).
  • Create a Connection Saves access to an outside data system with a Name and its Options (JSON), for use by datasets, atlases and targets.
  • Create a Dataset Defines a dataset from Identity Sets (JSON) and Options (JSON), reading through a Connection when one is set. Use Output to Streams (JSON) or Output to Traits (JSON) to send records on and Privacy to pick Suppress or Delete for data handling.
  • Create a Forecast Defines a forecast on a Stream and Stream Property Name, entered through an Entry Stream with a Horizon (JSON). Use Eligible Cohort, Predictors (JSON) or Currency to refine it.
  • Create a Persona Set Splits the people of a Cohort into personas. Set Number of Clusters to control how many groups form and Clustering Dimensions (JSON) to choose what they split on.
  • Create a Recommender Builds a recommender on a Stream and its Stream Property Name, with Predictors (JSON) and an optional Preview.
  • Create a Scope Defines a scope from a Population (JSON) listing its cohorts and a Payload (JSON) listing attributes and outcomes.
  • Create a Target Adds a target for a Scope with a Representation (JSON) and Options (JSON). Narrow the output with Filter (JSON) and Limit Rows (JSON), and set a Connection to deliver it elsewhere.
  • Create a Trait Creates a trait. Use Readable Name for the friendlier name shown in reports, Statistical Type and Unit to describe it and Lookup Table (JSON) to map values.
  • Create a Webhook Endpoint Subscribes a URL to the chosen Events, so Faraday sends a call there when they fire. The new endpoint comes with its Enabled events and Status.
  • Create an Account Sets up a new Faraday account with a Name. Use Branding (JSON) to pass its branding settings as a JSON object.
  • Create an Atlas Sets up an atlas using Options (JSON) for its source type and settings. Use Output to Locations (JSON) to map your columns to location fields and Connection to read from a data system.
  • Create an Attribute Defines an attribute in a Feature Store, fed by the Value Property Name of a Stream. Use Readable Name for the friendlier name shown in reports, Category and Tier to classify it and Statistical Type or Unit to describe its values.
  • Create an Outcome Defines an outcome from the Attainment Cohort of people who reached it. Use Feature Blocklist to leave features out by name, and Eligible Cohort, Attrition Cohort, Prediction Mode or Bias Mitigation (JSON) to refine it.
  • Delete a Cohort Deletes a cohort definition made of stream, place and location conditions.
  • Delete a Connection Removes a connection to an external data system.
  • Delete a Dataset Deletes a dataset that reads its records through a connection.
  • Delete a Forecast Removes a forecast that predicts from a stream over a horizon.
  • Delete a Persona Set Removes a persona set that was clustered from a cohort.
  • Delete a Recommender Deletes a recommender built on a stream.
  • Delete a Scope Removes a scope, the population and payload definition that targets deliver.
  • Delete a Stream Deletes a stream of records from Faraday.
  • Delete a Target Removes a target defined on a scope.
  • Delete a Trait Removes a trait that holds a statistical type and unit.
  • Delete a Webhook Endpoint Removes a webhook endpoint that receives Faraday events at a URL.
  • Delete an Account Deletes an account from the Faraday platform.
  • Delete an Atlas Deletes an atlas definition from Faraday.
  • Delete an Attribute Removes an attribute from its feature store.
  • Delete an Outcome Deletes an outcome defined by an attainment cohort.
  • Delete an Upload Deletes a stored file from your Faraday uploads.
  • Download a Target CSV Downloads the output of a target as a CSV file you can pass to other modules.
  • Download an Upload Downloads a stored file from your Faraday uploads and returns it as a File.
  • Find or Create a Stream Looks up a stream and creates it when none exists, returning its record either way.
  • Force Update a Cohort Requests a fresh cohort build and reports the Cohort id.
  • Force Update a Connection Starts another run of a connection and reports Success with its Connection id.
  • Force Update a Dataset Rebuilds a dataset straight away and reports Success with the Dataset id.

Microsoft Reports modules

  • List Directory Audits Reads the directory audit log. Each entry shows its Category, Activity display name, Activity date time, Result, who it was Initiated by and the Target resources it touched. Use Limit to cap the entries.
  • List Relying Parties Information Summarizes sign-ins per relying party over the reporting Period. Each entry shows the Relying party name, Successful sign in count, Failed sign in count, Sign in success rate and Migration status. Use Limit to end the list after a set number of parties.
  • List User Registration Details Reports how each user is set up for multi-factor authentication (MFA) and self-service password reset (SSPR). Use Is MFA Registered, Is SSPR Enabled or Methods Registered to narrow the report, and User Principal Name to find a single user.
  • Make an API Call Makes an authorized free-form request to the Microsoft Reports REST API with your saved credential.
  • Retrieve a Directory Audit Fetches one directory audit entry by its Directory Audit ID. The entry has the Category, Correlation ID, Result reason, Logged by service and any Additional details recorded for the activity.
  • Retrieve User Features Counts how many users are registered for each authentication feature. Use Included User Types and Included User Roles to count a narrower group. Output includes the Total user count.
  • Retrieve User Registration Details Gets the registration record of one user from the User ID. It shows whether the user is an admin, is registered or capable for MFA and SSPR, and is Passwordless capable.
  • Retrieve User Registration Methods Counts how many users registered each authentication method. Set Included User Roles or Included User Types to count only one group of users.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Faraday and Microsoft Reports integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Faraday and Microsoft Reports on WEXTL®

Claim your 3-day trial to build Faraday with Microsoft Reports integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Faraday and Microsoft Reports.

How do I connect Faraday and Microsoft Reports?

Connect your Faraday and Microsoft Reports accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Faraday and Microsoft Reports?

Example: when the "Watch Events" trigger in Faraday fires, WEXTL can "List Directory Audits" in Microsoft Reports. Faraday has 1 trigger (including Watch Events). Microsoft Reports has 8 actions (including List Directory Audits, List Relying Parties Information, and List User Registration Details). Add filters and transforms between steps when you need them.[1]

Can Faraday trigger actions in Microsoft Reports, and Microsoft Reports in Faraday?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Faraday and Microsoft Reports?

No. Faraday-to-Microsoft Reports automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Faraday integrate with Microsoft Reports in real time?

Yes. Trigger-based automations start the moment Faraday (or Microsoft Reports) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Faraday + Microsoft Reports integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Faraday with Microsoft Reports?

You can build your Faraday + Microsoft Reports automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Faraday and Microsoft Reports integration.

  1. Faraday and Microsoft Reports integration source code, module specs and credentials implementation.
  2. Our Faraday and Microsoft Reports integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Faraday and Microsoft Reports, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Faraday integration information
  6. Microsoft Reports integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Faraday and Microsoft Reports integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Faraday and Microsoft Reports, or get started